Details
Major Description
When a RPC connection was created from any table connection (e.g. via ConnectionFactory.createConnection(conf)), the SaslClientAuthenticationProviders that matches different authentication selector per-user/TOKEN as the singleton object and reuses for any followup connection creation.
If user want to create another connection with a different configuration key that the authentication selector may use, e.g. if one want to switch between secure and non-secure connection, it cannot be done because of the cached singleton instance of AuthenticationProviders.
the goal of this JIRA is to allow the RpcConnection and AuthenticationProviders align with whatever passing configuration object