Skip to content

Commit 7a4a43b

Browse files
authored
Merge pull request #259348 from veyaddan/vy-main1
authn changes
2 parents 481ab7c + ea7136f commit 7a4a43b

File tree

2 files changed

+15
-5
lines changed

2 files changed

+15
-5
lines changed
Loading

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

Lines changed: 15 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,10 @@ We support authentication of clients using X.509 certificates. X.509 certificat
1919
## Supported authentication modes
2020

2121
- Certificates issued by a Certificate Authority (CA)
22-
- Self-signed client certificate - thumbprint based authentication
22+
- Self-signed client certificate - thumbprint
23+
- Microsoft Entra ID token
2324

24-
**Certificate Authority (CA) signed certificates:**
25+
### Certificate Authority (CA) signed certificates:
2526

2627
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.
2728

@@ -35,9 +36,9 @@ While registering clients, you need to identify the certificate field used to ho
3536

3637
:::image type="content" source="./media/mqtt-client-authentication/mqtt-client-certificate-chain-authentication-options.png" alt-text="Screenshot showing the client metadata with the five certificate chain based validation schemes.":::
3738

38-
**Self-signed client certificate - thumbprint based authentication:**
39+
### Self-signed client certificate - thumbprint
3940

40-
Clients are onboarded to the service using the certificate thumbprint alongside the identity record. In this method of authentication, the client registry stores the exact thumbprint of the certificate that the client is going to use to authenticate. When client tries to connect to the service, service validates the client by comparing the thumbprint presented in the client certificate with the thumbprint stored in client metadata.
41+
In this method of authentication, the client registry stores the exact thumbprint of the certificate that the client is going to use to authenticate. When client tries to connect to the service, service validates the client by comparing the thumbprint presented in the client certificate with the thumbprint stored in client metadata.
4142

4243
:::image type="content" source="./media/mqtt-client-authentication/mqtt-client-metadata-thumbprint.png" alt-text="Screenshot showing the client metadata with thumbprint authentication scheme.":::
4344

@@ -59,7 +60,8 @@ while authenticating the client connection,
5960

6061
In both modes of client authentication, we expect the client authentication name to be provided either in the username field of the connect packet or in one of the client certificate fields.
6162

62-
### Supported client certificate fields for alternative source of client authentication name
63+
**Supported client certificate fields for alternative source of client authentication name**
64+
6365
You can use one of the following fields to provide client authentication name in the client certificate.
6466

6567
| Authentication name source option | Certificate field | Description |
@@ -70,6 +72,13 @@ You can use one of the following fields to provide client authentication name in
7072
| Certificate Ip | tls_client_auth_san_ip | The IPv4 or IPv6 address present in the iPAddress SAN entry in the certificate. |
7173
| Certificate Email | tls_client_auth_san_email | The rfc822Name SAN entry in the certificate. |
7274

75+
76+
77+
### Microsoft Entra ID token
78+
79+
You can authenticate MQTT clients with Microsoft Entra JWT to connect to Event Grid namespace. You can use Azure role-based access control (Azure RBAC) to enable MQTT clients, with Microsoft Entra identity, to publish or subscribe access to specific topic spaces.
80+
81+
7382
## High level flow of how mutual transport layer security (mTLS) connection is established
7483

7584
To establish a secure connection with MQTT broker, you can use either MQTTS over port 8883 or MQTT over web sockets on port 443. It's important to note that only secure connections are supported. The following steps are to establish secure connection prior to the client authentication.
@@ -88,3 +97,4 @@ To establish a secure connection with MQTT broker, you can use either MQTTS over
8897

8998
## Next steps
9099
- Learn how to [authenticate clients using certificate chain](mqtt-certificate-chain-client-authentication.md)
100+
- Learn how to [authenticate client using Microsoft Entra ID token](mqtt-client-azure-ad-token-and-rbac.md)

0 commit comments

Comments
 (0)