Skip to content

Commit 89a2f6d

Browse files
committed
Fix tab block
1 parent 2cc1aa6 commit 89a2f6d

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.subservice: azure-mqtt-broker
88
ms.topic: how-to
99
ms.custom:
1010
- ignite-2023
11-
ms.date: 12/03/2024
11+
ms.date: 12/09/2024
1212

1313
#CustomerIntent: As an operator, I want to configure authentication so that I have secure MQTT broker communications.
1414
---
@@ -17,7 +17,7 @@ ms.date: 12/03/2024
1717

1818
[!INCLUDE [kubernetes-management-preview-note](../includes/kubernetes-management-preview-note.md)]
1919

20-
MQTT broker supports multiple authentication methods for clients, and you can configure each listener port to have its own authentication settings with a *BrokerAuthentication* resource. For a list of the available settings, see the [Broker Authentication](/rest/api/iotoperationsmq/broker-authentication) API reference.
20+
MQTT broker supports multiple authentication methods for clients, and you can configure each listener port to have its own authentication settings with a *BrokerAuthentication* resource. For a list of the available settings, see the [Broker Authentication](/rest/api/iotoperations/broker-authentication) API reference.
2121

2222
## Link BrokerListener and BrokerAuthentication
2323

@@ -912,6 +912,8 @@ spec:
912912
header_key: header_value
913913
```
914914

915+
---
916+
915917
## Disable authentication
916918

917919
For testing, you can disable authentication for a broker listener port. Disabling authentication isn't recommended for production environments.

0 commit comments

Comments
 (0)