docs(scim): fix custom attribute extension URN#3334
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
NicolasLopes7
requested review from
gabrielmeloc22,
iagodahlem,
im2nguyen and
kalafut
NicolasLopes7
commented
Apr 30, 2026
gabrielmeloc22
approved these changes
Apr 30, 2026
NicolasLopes7
commented
Apr 30, 2026
The custom attribute mapping guide advertised a fictional schema URN (urn:clerk:scim:schemas:extension:custom:2.0:User) and used the standard enterprise extension in its example path. The backend actually advertises urn:ietf:params:scim:schemas:extension:clerk:2.0:User and accepts any SCIM path the IdP sends (top-level, nested, or any extension namespace).
NicolasLopes7
force-pushed
the
nicolas/scim-custom-attrs-fix
branch
from
642fc0d to
a7e8d4d
Compare
iagodahlem
approved these changes
Apr 30, 2026
SarahSoutoul
approved these changes
Apr 30, 2026
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
4 participants
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
The custom attribute mapping guide had two factual errors that I caught while fact-checking against the backend:
urn:clerk:scim:schemas:extension:custom:2.0:User). The real URN that/Schemasadvertises and that user payloads accept isurn:ietf:params:scim:schemas:extension:clerk:2.0:User.urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department— which is the standard enterprise extension, not Clerk's. The backend accepts any path the IdP sends (top-level core attribute, nested, or any extension namespace).This PR:
title), a nested attribute (e.g.name.givenName), or any extension namespace.