Skip to content

feat(scim): add GET /scim/v2/Users/{id} - #2671

Open
xlgmokha wants to merge 6 commits into
xlgmokha/auth-1368afrom
xlgmokha/auth-1368b
Open

feat(scim): add GET /scim/v2/Users/{id}#2671
xlgmokha wants to merge 6 commits into
xlgmokha/auth-1368afrom
xlgmokha/auth-1368b

Conversation

@xlgmokha

@xlgmokha xlgmokha commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

What kind of change does this PR introduce?

Feature. Adds GET /scim/v2/Users/{id}, the first SCIM resource endpoint.

https://linear.app/supabase/issue/AUTH-1368/scim-users-get-by-id

What is the current behavior?

/scim/v2 serves the three discovery endpoints and nothing else.

What is the new behavior?

scim.Server.Authenticate resolves the SSO provider that owns the presented bearer token and puts it on the request context. UserByID then returns that provider's user:

case response
user belongs to the token's provider 200 + User resource, application/scim+json
missing, malformed, or unknown token 401 + WWW-Authenticate: Bearer
token resolves but the provider is disabled 403
unknown id, another provider's user, soft deleted user, malformed id 404, identical body

Discovery stays unauthenticated. Authenticate is scoped to the /Users route so a deployment with no provisioned tenant still serves /Schemas.

Additional context

@xlgmokha xlgmokha self-assigned this Aug 3, 2026
@xlgmokha
xlgmokha marked this pull request as ready for review August 3, 2026 21:06
@xlgmokha
xlgmokha requested a review from a team as a code owner August 3, 2026 21:06
@xlgmokha
xlgmokha force-pushed the xlgmokha/auth-1368b branch 2 times, most recently from bfdaf08 to edc69eb Compare August 4, 2026 16:43
@xlgmokha
xlgmokha force-pushed the xlgmokha/auth-1368b branch from edc69eb to eb57a35 Compare August 4, 2026 16:46
@xlgmokha
xlgmokha force-pushed the xlgmokha/auth-1368b branch 2 times, most recently from a66ea24 to b353b6d Compare August 4, 2026 17:27
@xlgmokha
xlgmokha force-pushed the xlgmokha/auth-1368b branch from b353b6d to 78515b5 Compare August 4, 2026 19:52
@xlgmokha
xlgmokha force-pushed the xlgmokha/auth-1368b branch from 78515b5 to f3d911f Compare August 4, 2026 20:05
@xlgmokha
xlgmokha force-pushed the xlgmokha/auth-1368b branch from f3d911f to 8f19172 Compare August 6, 2026 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant