oxidecomputer / oxidecomputer/omicron
Make e a plan for internal authz.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Recall that we don't have a plan for internal authz. So when I initially added the "internal API" user, I granted them all privileges by creating a built-in role assignment that grants this user the "fleet admin" role on the sole fleet.
After #1580, this no longer granted superuser privileges. The change in #1710 restores that previous behavior.
Longer term, of course we ought to have a plan for more restricted authz on the internal API.
Originally posted by @davepacheco in https://github.com/oxidecomputer/omicron/issues/1710#issuecomment-1246141454
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 this issue together with #1710 and #1580 to understand the internal API user's current fleet-admin role assignment and the restored superuser behavior. Define and document a plan for more restricted internal API authorization, with clear privilege boundaries and an agreed completion criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100