[stub] Synchronously initialize JWTAuthenticator and provide status
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 739
- Forks
- 85
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
Related to #260
In the v1.22 Kube library code, we can directly specify a oidc.KeySet and thus synchronously initialize the JWTAuthenticator. We can also use this to validate that the remote key set is reachable and functioning.
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 reading related issue #260 and the v1.22 Kube library context mentioned here. Determine how a synchronously initialized JWTAuthenticator should expose status and how remote key-set reachability is validated; the work is done when initialization and status reporting meet those requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100