Skip to content

Conversation

@spike83
Copy link
Contributor

@spike83 spike83 commented Apr 19, 2024

It looks like this is working fine except when you want to use the azure workload identity.
Inspired from https://github.com/nniikkoollaaii/workload-identity-kafka-sasl-oauthbearer I added support for azure workload identity.

@spike83 spike83 requested a review from a team as a code owner April 19, 2024 12:34
@spike83 spike83 changed the title added support for azure workload identity PoC added support for azure workload identity and schema registry PoC Apr 23, 2024
@spike83
Copy link
Contributor Author

spike83 commented Apr 23, 2024

Seems that SASL_OAUTHBEARER_INHERIT is not going to use AuthenticateCallbackHandler. So I've added a BearerAuthCredentialProvider to make sure we can also use the token for Schema Registry access.
confluentinc/schema-registry#3096

@spike83 spike83 force-pushed the aks-workload-id-support branch from e0bf40b to 92bf0da Compare April 24, 2024 07:57
@spike83
Copy link
Contributor Author

spike83 commented May 15, 2024

@javabrett is this of interests?

@javabrett
Copy link
Member

Yes thanks @spike83 - will take the time to review this now.

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

Successfully merging this pull request may close these issues.

2 participants