From 3caa4e0022c189482a35864484e23845f8cb9d1c Mon Sep 17 00:00:00 2001 From: Ivan Kozlovic Date: Wed, 26 May 2021 11:00:57 -0600 Subject: [PATCH] Remove "standard" mention for NATS clients --- nats-server/configuration/mqtt/mqtt_config.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nats-server/configuration/mqtt/mqtt_config.md b/nats-server/configuration/mqtt/mqtt_config.md index 3818932..24c6375 100644 --- a/nats-server/configuration/mqtt/mqtt_config.md +++ b/nats-server/configuration/mqtt/mqtt_config.md @@ -106,7 +106,7 @@ mqtt { In operator mode, all users need to provide a JWT in order to connect. For MQTT clients, it means that you need to pass the JWT token as the MQTT password and use any username since MQTT protocol requires a username to be set if a password is set. -In this mode, standard NATS clients are required to sign a `nonce` sent by the server using their private key (see [JWTs and Privacy](../securing_nats/jwt#jwts-and-privacy)). Of course MQTT clients cannot do that, therefore, in order for the JWT to be accepted by the server without the need of signing the `nonce`, the JWT has to have the `Bearer` boolean set to true. +In this mode, NATS clients are required to sign a `nonce` sent by the server using their private key (see [JWTs and Privacy](../securing_nats/jwt#jwts-and-privacy)). Of course MQTT clients cannot do that, therefore, in order for the JWT to be accepted by the server without the need of signing the `nonce`, the JWT has to have the `Bearer` boolean set to true. ### Local mode