oxidecomputer / oxidecomputer/oidcx
Periodic OIDC configuration fetching
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 0
- Avg merge
- 3m
- Merged PRs (30d)
- 5
Description
Currently we fetch a remote providers OIDC configuration at startup. We need to periodically refresh this data in the background as it can change on the remote side at any time.
Contributor guide
No contributing guide indexed for this repository
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 at the startup path that fetches the remote provider's OIDC configuration and trace how that data is consumed. Determine the background refresh lifecycle and verify that remote configuration changes are picked up without restarting the service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100