redpanda-data / redpanda-data/redpanda
private_key_jwt JWKS support for Generic OIDC connect
Open
Nobody has claimed this yet.
kind/enhance
- Dominant language
- C++
- Stars
- 12.6k
- Forks
- 792
- PR merge metrics
- No merged PRs in 30d
Description
Strong authentication is expected in the enterprise environment, so also with OIDC, JWKS AUTH should be an auth option for OIDC server connection, in addition to the current clientID +secret
Why is solving this problem impactful?
Higher security standard
Additional notes
JIRA Link: CORE-8729
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 Generic OIDC server connection handling and the existing clientID + secret authentication path. Review the linked JWKS endpoint documentation, then define the work as adding private_key_jwt JWKS authentication while preserving the current option; done means OIDC connections can use JWKS authentication successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100