redpanda-data / redpanda-data/console
Internal client schema Registry oidc authentication not supported
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 432
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 40
Description
I recently migrated schema registry to only support authentication via oauth, but when I tried to change redpanda console to authenticate my internal client in schema registry via oidc, I could only find a schema registry configuration for basic auth or using a bearer token directly, but there are no properties for clientId, clientSecret and issuerUrl.
Is there no way to authenticate an internal client to schema registry via oidc with the properties mentioned above right now? And if there isn't, are there any plans to support it soon?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the schema registry client configuration and the existing basic-auth and bearer-token settings. Check how authentication is created for internal clients and determine the scope needed for clientId, clientSecret, and issuerUrl; done means an OIDC-authenticated schema registry connection works through the Console configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100