Open eolivelli opened 2 years ago
Pulsar client supports OAuth2 client authentication https://pulsar.apache.org/docs/security-oauth2/
and you can already use it by configuring the PulsarConnectionFactory via authPlugin and authParams.
but there is a request to support it while using ConnectionFactory#createConnection(username/password).
the most straight forward way of mapping OAuth2 client credentials is to map:
and leave all the other parameters to be set in the ConnectionFactory configuration:
The JMS client will create the "credentials" to be passed to the the AuthenticationFactoryOAuth2.clientCredentials method
AuthenticationFactoryOAuth2.clientCredentials
@eolivelli - yes, I think these configuration options make sense. The scope, audience, and client_email are optional for some identity providers, so we'll want to treat the as optional.
Pulsar client supports OAuth2 client authentication https://pulsar.apache.org/docs/security-oauth2/
and you can already use it by configuring the PulsarConnectionFactory via authPlugin and authParams.
but there is a request to support it while using ConnectionFactory#createConnection(username/password).
the most straight forward way of mapping OAuth2 client credentials is to map:
and leave all the other parameters to be set in the ConnectionFactory configuration:
The JMS client will create the "credentials" to be passed to the the
AuthenticationFactoryOAuth2.clientCredentials
method