Skip to content

Commit 3789412

Browse files
authored
Fix typo and confusing order
1 parent 842e4b6 commit 3789412

File tree

1 file changed

+17
-19
lines changed

1 file changed

+17
-19
lines changed

articles/iot-operations/manage-mqtt-connectivity/howto-configure-authentication.md

Lines changed: 17 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.subservice: azure-mqtt-broker
77
ms.topic: how-to
88
ms.custom:
99
- ignite-2023
10-
ms.date: 11/15/2023
10+
ms.date: 6/27/2023
1111

1212
#CustomerIntent: As an operator, I want to configure authentication so that I have secure MQTT broker communications.
1313
---
@@ -119,7 +119,7 @@ Each client has the following required properties:
119119
- Password ([PBKDF2 encoded](https://en.wikipedia.org/wiki/PBKDF2))
120120
- [Attributes for authorization](./howto-configure-authorization.md)
121121

122-
For example, start with a `clients.toml` with identities and PBKDF2 encoded passwords.
122+
For example, start with a `passwords.toml` with identities and PBKDF2 encoded passwords.
123123

124124
```toml
125125
# Credential #1
@@ -143,27 +143,13 @@ floor = "floor2"
143143
site = "site1"
144144
```
145145

146-
To encode the password using PBKDF2, use the [Azure IoT Operations CLI extension](/cli/azure/iot/ops) that includes the `az iot ops mq get-password-hash` command. It generates a PBKDF2 password hash from a password phrase using the SHA-512 algorithm and a 128-bit randomized salt.
147-
148-
```bash
149-
az iot ops mq get-password-hash --phrase TestPassword
150-
```
151-
152-
The output shows the PBKDF2 password hash to copy:
153-
154-
```json
155-
{
156-
"hash": "$pbkdf2-sha512$i=210000,l=64$4SnaHtmi7m++00fXNHMTOQ$rPT8BWv7IszPDtpj7gFC40RhhPuP66GJHIpL5G7SYvw+8rFrybyRGDy+PVBYClmdHQGEoy0dvV+ytFTKoYSS4A"
157-
}
158-
```
159-
160-
Then, save the file as `passwords.toml` and import it into a Kubernetes secret under that key.
146+
Then, import it into a Kubernetes secret under that key.
161147

162148
```bash
163149
kubectl create secret generic passwords-db --from-file=passwords.toml -n azure-iot-operations
164150
```
165151

166-
Include a reference to the secret in the *BrokerAuthentication* custom resource
152+
Include a reference to the secret in the *BrokerAuthentication* custom resource.
167153

168154
```yaml
169155
spec:
@@ -172,7 +158,19 @@ spec:
172158
secretName: passwords-db
173159
```
174160

175-
It might take a few minutes for the changes to take effect.
161+
To encode the password using PBKDF2, use the [Azure IoT Operations CLI extension](/cli/azure/iot/ops) that includes the `az iot ops mq get-password-hash` command. It generates a PBKDF2 password hash from a password phrase using the SHA-512 algorithm and a 128-bit randomized salt.
162+
163+
```bash
164+
az iot ops mq get-password-hash --phrase TestPassword
165+
```
166+
167+
The output shows the PBKDF2 password hash to copy:
168+
169+
```json
170+
{
171+
"hash": "$pbkdf2-sha512$i=210000,l=64$4SnaHtmi7m++00fXNHMTOQ$rPT8BWv7IszPDtpj7gFC40RhhPuP66GJHIpL5G7SYvw+8rFrybyRGDy+PVBYClmdHQGEoy0dvV+ytFTKoYSS4A"
172+
}
173+
```
176174

177175
You can use Azure Key Vault to manage secrets for Azure IoT MQ instead of Kubernetes secrets. To learn more, see [Manage secrets using Azure Key Vault or Kubernetes secrets](../manage-mqtt-connectivity/howto-manage-secrets.md).
178176

0 commit comments

Comments
 (0)