oxidecomputer / oxidecomputer/console
SCIM support
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 32
Description
The new feature allows silo groups and users to be imported into Oxide from the linked external IDP via the SCIM user and group CRUD API. As opposed to JIT, the updates can be pushed by the IDP (not polled by Oxide) any time without the user logging in. The API calls are authenticated via a bearer token that gets generated when a silo backed by SCIM is created. Silo admin can subsequently view/rotate the token via a set of CRUD API.
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
No files, tests, or existing entry points are named. Start from the requested SCIM user and group CRUD API and the silo admin operations for viewing and rotating bearer tokens. Done means external identity providers can push user and group updates, with authenticated token management for SCIM-backed silos.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, authorization, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100