Skip to content

Commit 808e8d3

Browse files
committed
Fixed issues
1 parent 11e30be commit 808e8d3

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

articles/event-grid/mqtt-client-authentication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.subservice: mqtt
1313

1414
# Client authentication
1515

16-
Azure Event Grid's MQTT broken supports the following authentication modes.
16+
Azure Event Grid's MQTT broker supports the following authentication modes.
1717

1818
- Certificate-based authentication
1919
- Microsoft Entra ID authentication

articles/event-grid/mqtt-client-certificate-authentication.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.author: geguirgu
88
ms.subservice: mqtt
99
---
1010

11-
# MQTT Client authentication using certificates
11+
# MQTT client authentication using certificates
1212

1313
Azure Event Grid's MQTT broker supports authentication of clients using X.509 certificates. X.509 certificate provides the credentials to associate a particular client with the tenant. In this model, authentication generally happens once during session establishment. Then, all future operations using the same session are assumed to come from that identity.
1414

@@ -20,12 +20,12 @@ Supported authentication modes are:
2020

2121
This article focuses on certificates. To learn about authentication using Microsoft Entra ID tokens, see [authenticate client using Microsoft Entra ID token](mqtt-client-azure-ad-token-and-rbac.md).
2222

23-
## Certificate Authority (CA) signed certificates:
23+
## Certificate Authority (CA) signed certificates
2424

2525
In this method, a root or intermediate X.509 certificate is registered with the service. Essentially, the root or intermediary certificate that is used to sign the client certificate, must be registered with the service first.
2626

2727
> [!IMPORTANT]
28-
> - Ensure to upload the root or intemediate certificate that is used to sign the client certificate. It is not needed to upload the entire certificate chain.
28+
> - Ensure to upload the root or intermediate certificate that is used to sign the client certificate. It is not needed to upload the entire certificate chain.
2929
> - For example, if you have a chain of root, intermediate, and leaf certificates, ensure to upload the intermediate certificate that signed the leaf/client certificates.
3030
3131
:::image type="content" source="./media/mqtt-client-authentication/mqtt-creating-certificate-chain.png" alt-text="Screenshot showing the CA certificates page with root and intermediate certificates used to sign the client certificates.":::

articles/event-grid/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ items:
6767
- name: MQTT client authentication
6868
href: mqtt-client-authentication.md
6969
items:
70-
- name: MQTT Client authentication using certificates
70+
- name: MQTT client authentication using certificates
7171
href: mqtt-client-certificate-authentication.md
7272
- name: JWT authentication and RBAC authorization for clients with Microsoft Entra identity
7373
href: mqtt-client-microsoft-entra-token-and-rbac.md

0 commit comments

Comments
 (0)