[stub] Support static key set with JWTAuthenticator
Open
Nobody has claimed this yet.
enhancement
priority/undecided
- Dominant language
- Go
- Stars
- 739
- Forks
- 85
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
In the v1.22 Kube library code, we can directly specify a oidc.KeySet and initialize the JWTAuthenticator with a static (i.e. inline instead of fetched via the network) key set (to support different network typologies).
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 in the v1.22 Kube library code and trace how JWTAuthenticator is initialized and how its oidc.KeySet is obtained. The work is done when JWTAuthenticator supports a static, inline key set as well as the existing network-fetched setup, including coverage for the new initialization path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100