Skip to content

Schema registry server side Oauth2 enablement #3653

Open
@maverickode

Description

@maverickode

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"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions