Skip to content

Schema registry server side Oauth2 enablement #3653

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

Open
maverickode opened this issue Apr 7, 2025 · 0 comments
Open

Schema registry server side Oauth2 enablement #3653

maverickode opened this issue Apr 7, 2025 · 0 comments

Comments

@maverickode
Copy link

maverickode commented Apr 7, 2025

I want all communication to schema registry protected by Oauth2. I configured Oauth2 using following configurations but something is still missing.

rest.servlet.initializor.classes=io.confluent.common.security.jetty.initializer.AuthenticationHandler
oauthbearer.jwks.endpoint.url=/certs
oauthbearer.expected.issuer=
/auth/realms/**
oauthbearer.expected.audience="account"
oauthbearer.sub.claim.name="sub"
oauthbearer.groups.claim.name="groups"

Upon accessing an endpoint I get following response while the token is valid. What is this realm configuration that it complaints about?

Bearer realm="null",error="invalid_token"

@maverickode maverickode changed the title Schema registry server side Oauth enablement Schema registry server side Oauth2 enablement Apr 8, 2025
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