Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AuthenticateCallbackHandler not supported with SASL_OAUTHBEARER_INHERIT credential source #3096

Open
spike83 opened this issue Apr 23, 2024 · 0 comments

Comments

@spike83
Copy link

spike83 commented Apr 23, 2024

For the Kafka client I'm using the following setting.

sasl.login.callback.handler.class=io.confluent.oauth.azure.managedidentity.OAuthBearerLoginCallbackHandler

With this I can provide a token e.g. for a Pod Identity in Azure. But when I want to configure the schema registry to use the same mechanism this seems not to be picked up.
See repos here: https://github.com/confluentinc/confluent-oauth-extensions

The docs state that SASL_OAUTHBEARER_INHERIT should pick up the same oauth configuration as Kafka

To inherit the OAuth configuration settings from your Kafka configuration, add the following configuration settings to your Schema Registry client:

bearer.auth.credentials.source=SASL_OAUTHBEARER_INHERIT
bearer.auth.logical.cluster=<lsrc-resource-id>

from: https://docs.confluent.io/cloud/current/access-management/authenticate/oauth/configure-clients-oauth.html#client-login-callback-handler-top-level-configuration-options

For the moment I think I could just re-implement it as a CustomBearerAuthCredentialProvider. But I think the expectation on SASL_OAUTHBEARER_INHERIT should be that this would work without and also picks up the implementations of AuthenticateCallbackHandler from the Kafka client.

Or did I miss something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant