You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-operations/discover-manage-assets/howto-configure-opcua-authentication-options.md
+23-78Lines changed: 23 additions & 78 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,81 +32,26 @@ A deployed instance of Azure IoT Operations Preview. To deploy Azure IoT Operati
32
32
33
33
## Configure username and password authentication
34
34
35
-
First, configure the secrets for the username and password in Azure Key Vault and project them into the connected cluster by using a `SecretProviderClass` object.
36
-
37
-
1. Configure the username and password in Azure Key Vault. In the following example, use the `username` and `password` as secret references for the asset endpoint configuration in the operations experience web UI.
38
-
39
-
Replace the placeholders for username and password with the credentials used to connect to the OPC UA server.
40
-
41
-
To configure the username and password, run the following code:
42
-
43
-
# [Bash](#tab/bash)
44
-
45
-
```bash
46
-
# Create username Secret in Azure Key Vault
47
-
az keyvault secret set \
48
-
--name username \
49
-
--vault-name <your-azure-key-vault-name> \
50
-
--value <your-opc-ua-server-username> \
51
-
--content-type text/plain
52
-
53
-
# Create password Secret in Azure Key Vault
54
-
az keyvault secret set \
55
-
--name password \
56
-
--vault-name <your-azure-key-vault-name> \
57
-
--value <your-opc-ua-server-password> \
58
-
--content-type text/plain
59
-
```
60
-
61
-
# [PowerShell](#tab/powershell)
62
-
63
-
```powershell
64
-
# Create username Secret in Azure Key Vault
65
-
az keyvault secret set`
66
-
--name username `
67
-
--vault-name <your-azure-key-vault-name>`
68
-
--value <your-opc-ua-server-username>`
69
-
--content-type text/plain
70
-
71
-
# Create password Secret in Azure Key Vault
72
-
az keyvault secret set`
73
-
--name password `
74
-
--vault-name <your-azure-key-vault-name>`
75
-
--value <your-opc-ua-server-password>`
76
-
--content-type text/plain
77
-
```
78
-
79
-
---
80
-
81
-
1. Configure the `aio-opc-ua-broker-user-authentication` custom resource in the cluster. Use a Kubernetes client such as `kubectl` to configure the `username` and `password` secrets in the `SecretProviderClass` object array in the cluster.
82
-
83
-
The following example shows a complete`SecretProviderClass` custom resource after you add the secrets:
84
-
85
-
```yaml
86
-
apiVersion: secrets-store.csi.x-k8s.io/v1
87
-
kind: SecretProviderClass
88
-
metadata:
89
-
name: aio-opc-ua-broker-user-authentication
90
-
namespace: azure-iot-operations
91
-
spec:
92
-
provider: azure
93
-
parameters:
94
-
usePodIdentity: 'false'
95
-
keyvaultName: <azure-key-vault-name>
96
-
tenantId: <azure-tenant-id>
97
-
objects: |
98
-
array:
99
-
- |
100
-
objectName: username
101
-
objectType: secret
102
-
objectVersion: ""
103
-
- |
104
-
objectName: password
105
-
objectType: secret
106
-
objectVersion: ""
107
-
```
108
-
109
-
> [!NOTE]
110
-
> The time it takes to project Azure Key Vault certificates into the cluster depends on the configured polling interval.
111
-
112
-
In the operations experience, selectthe**Username & password** option when you configure the Asset endpoint. Enter the names of the references that store the username and password values. In this example, the names of the references are `username` and `password`.
35
+
First, configure the secrets for the username and password in Azure Operator Experience.
36
+
37
+
Step 1: Navigate to the Asset EndPoint Profile from the left side menu
0 commit comments