docs(scim): clarify directory sync custom attribute paths#3345
Draft
NicolasLopes7 wants to merge 1 commit intomainfrom
Draft
docs(scim): clarify directory sync custom attribute paths#3345NicolasLopes7 wants to merge 1 commit intomainfrom
NicolasLopes7 wants to merge 1 commit intomainfrom
Conversation
The directory sync guide still advertised the wrong custom extension URN (urn:clerk:scim:schemas:extension:custom:2.0:User) and implied the mapping only worked through that namespace. Aligns with #3334: the backend resolves any SCIM path the IdP sends — top-level, nested, or under any extension namespace, including the standard enterprise extension and Clerk's custom extension.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
Follow-up to #3334. The directory sync guide still advertised the wrong custom extension URN (
urn:clerk:scim:schemas:extension:custom:2.0:User) and implied custom attributes only worked through that namespace.Backend behavior:
scim_pathresolves any field on the SCIM user payload via gjson — top-level core attributes, nested attributes, or anything under an extension namespace (standard enterprise extension or Clerk's custom extension).Changes
urn:ietf:params:scim:schemas:extension:clerk:2.0:User.Test plan