Search before asking
Description
Currently, we support client.security.sasl.username and client.security.sasl.password. Unlike Kafka, our server does not support custom SASL mechanisms—instead, we provide a more flexible, plugin-based authentication system. As a result, client.security.sasl.jaas.config is no longer necessary.
However, for backward compatibility, client.security.sasl.jaas.config must still be retained. Since only SASL/PLAIN is currently supported, we can minimize the scope of this configuration to PlainLoginModule only.
Willingness to contribute
Search before asking
Description
Currently, we support
client.security.sasl.usernameandclient.security.sasl.password. Unlike Kafka, our server does not support custom SASL mechanisms—instead, we provide a more flexible, plugin-based authentication system. As a result,client.security.sasl.jaas.configis no longer necessary.However, for backward compatibility,
client.security.sasl.jaas.configmust still be retained. Since onlySASL/PLAIN is currently supported, we can minimize the scope of this configuration toPlainLoginModuleonly.Willingness to contribute