Skip to content

docs: added docs for scim mapper now receiving identity #2612

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
deepakprabhakara merged 1 commit into from
Jun 8, 2026
Merged

docs: added docs for scim mapper now receiving identity #2612

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions docs/kratos/manage-identities/50_scim.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,27 @@ to the [SCIM user resource schema](https://datatracker.ietf.org/doc/html/rfc7643

The script should return a JSON object as defined in the [Jsonnet reference](../reference/jsonnet#output).

The SCIM provisioning data mapper also receives the existing `identity` (if present) through a new identity external variable,
alongside the existing scim variable. It exposes traits, metadata_public, and metadata_admin, each defaulting to an empty object
when unset.

This lets a mapper preserve or merge attributes that SCIM does not manage. A mapper can now merge them back in:

```
local scim = std.extVar('scim');
local identity = std.extVar('identity');
local existingPublic = std.get(identity, 'metadata_public', {});

{
identity: {
...
metadata_public: existingMetadata + {
// Add or override only what SCIM should manage
},
},
}
```

### Use the SCIM client

Once you have configured a SCIM client, you can use it to provision identities. The Ory Network SCIM server provides a set of
Expand Down
Loading