feat: SCIM discover endpoints#2643
Draft
xlgmokha wants to merge 6 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Implements the three SCIM discovery/metadata endpoints behind the experimental feature flag from #2639:
GET /scim/v2/ServiceProviderConfigGET /scim/v2/ResourceTypesGET /scim/v2/SchemasThese replace the
501 Not Implementedstubs from #2639 with real, spec-shaped JSON.What is the current behavior?
With #2639 alone, the three routes above mount when the flag is on, but each just returns a bare 501 with no body.
What is the new behavior?
Each endpoint now returns real RFC 7643-shaped JSON:
ServiceProviderConfigreports this server's actual current capabilities —patch,bulk,filter,changePassword,sort, andetagare allsupported: falsefor now, since none of that is implemented yet.authenticationSchemesdescribes the bearer-token scheme a later PR will enforce.ResourceTypesandSchemasreturn an emptyResources: []list, since no resource types (Users, Groups) exist yet.Nothing here is reachable unless
GOTRUE_EXPERIMENTAL_SCIM_ENABLEDis set, and there's no behavior change outside/scim/v2/*.Additional context
Stacked on #2639, so the diff only shows what's new here. It'll get retargeted once #2639 merges. Part of a series of small PRs building out SCIM support incrementally.