supabase / auth / 30364523892 / 1
72%
master: 72%

DEFAULT BRANCH: master
Ran
Files 197
Run time 5s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 72.16% (+0.03%) from 72.126%
30364523892.1

push

github

web-flow 
feat: gate SCIM router behind an experimental feature flag (#2639)

## What kind of change does this PR introduce?

Add `GOTRUE_EXPERIMENTAL_SCIM_ENABLED` (default false) to conditionally
mount `/scim/v2/*`, the first step toward SCIM (System for Cross-domain
Identity Management) support for provisioning and deprovisioning users
from an identity provider.

Ships dark: with the flag off, no SCIM routes are reachable; with it on,
the router mounts three stub endpoints (ServiceProviderConfig,
ResourceTypes, Schemas) that return 501 until real handlers land in
follow-up PRs.

## What is the current behavior?

Currently, we do not have SCIM support. There is no `/scim/v2` router
and no way for an identity provider to provision or deprovision users
automatically.

https://linear.app/supabase/issue/AUTH-1361/enable-scim-via-feature-flag

## What is the new behavior?

This is the first step towards adding SCIM support: a feature flag that
gates the `/scim/v2` router, shipped dark with no customer-facing toggle
yet, so it can be verified internally before real per-provider
enablement is added.

## Additional context

This reimplements a smaller, subset of SCIM support. It draws on ideas
and endpoint shapes explored in two earlier PRs:

* https://github.com/supabase/auth/pull/2115: DB-backed multi-tenant
SCIM provider model
* https://github.com/supabase/auth/pull/2309: Full Users/Groups CRUD, a
SCIM-specific error schema, and Admin API integration

18325 of 25395 relevant lines covered (72.16%)

682.25 hits per line

Source Files on job 30364523892.1