oxidecomputer / oxidecomputer/omicron
implement OAuth refresh tokens
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
We do not currently implement OAuth refresh tokens. Clients are supposed to get a refresh token and use that to obtain a new access token before their current access token expires. Refresh tokens are currently not needed because we also haven't implemented #2302. But we're presumably going to need that for MVP, and then I think we're going to want this.
(edit: this comment was removed under https://github.com/oxidecomputer/omicron/pull/2417 but the issue remains)
CC @plotnick
See also #2302.
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 with nexus/types/src/external_api/views.rs around line 419 and read issue #2302, since the issue says refresh tokens depend on that work. Map the existing OAuth access-token flow and define completion as clients receiving refresh tokens and using them to obtain new access tokens before expiration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100