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

Co-authored-by: John Lian <[email protected]>

Author: gordonwang0

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

@@ -163,7 +163,7 @@ The earlier example specifies custom and SAT. When a client connects, MQTT broke
 
 1. MQTT broker checks if the client's credentials are valid for custom authentication. Since custom authentication relies on an external server to determine validity of credentials, the broker considers all credentials relevant to custom auth and forwards them to the custom authentication server.
 1. If the custom authentication server responds with `Pass` or `Fail` result, the authentication flow ends. However, if the custom authentication server isn't available, then MQTT broker falls back to the remaining specified methods, with SAT being next.
-1. MQTT broker tries to authenticate the credentials as SAT credentials. If the MQTT username starts with `K8S-SAT`, MQTT broker evaluates the MQTT password as a SAT.
+1. MQTT broker tries to authenticate the credentials as SAT credentials.
 
 If the custom authentication server is unavailable and all subsequent methods determine that the provided credentials aren't relevant, then the broker denies the client connection.