Skip to content

docs(scim): drop URN requirement for custom attribute paths#3346

Draft
NicolasLopes7 wants to merge 1 commit intomainfrom
nicolas/custom-attrs-no-urn
Draft

docs(scim): drop URN requirement for custom attribute paths#3346
NicolasLopes7 wants to merge 1 commit intomainfrom
nicolas/custom-attrs-no-urn

Conversation

@NicolasLopes7
Copy link
Copy Markdown
Contributor

@NicolasLopes7 NicolasLopes7 commented May 6, 2026

What does this solve? What changed?

Clerk's SCIM endpoint now accepts any attribute path and maps it directly to publicMetadata, so the docs no longer need to prescribe Clerk's custom extension URN (urn:ietf:params:scim:schemas:extension:clerk:2.0:User).

Removed URN-specific language and examples from the custom attribute mapping and directory sync pages, replacing them with general guidance that any SCIM path (core, nested, or extension) works.

  • Updated custom-attribute-mapping.mdx SCIM section + Okta example
  • Updated directory-sync.mdx SCIM mapping section + Okta example

Clerk's SCIM endpoint now accepts any attribute path and maps it to
publicMetadata, so the docs no longer prescribe Clerk's custom extension
URN. Generalize the guidance and examples in the custom attribute
mapping and directory sync pages.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 6, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
clerk-docs Ready Ready Preview May 6, 2026 3:22pm

Request Review

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