Skip to content

Conversation

@Karuna-Mendix
Copy link
Collaborator

@Karuna-Mendix Karuna-Mendix commented Jan 21, 2026

@Karuna-Mendix Karuna-Mendix self-assigned this Jan 21, 2026
The typical example of this scenario includes Okta as an IdP and using `sub` as a unique identifier. In the OIDC **Attribute Mapping** configuration, the unique IdP claim `sub` is stored in the `System.User.Name` attribute of the Mendix user entity, and the `Name` attribute is configured as the OIDC principal attribute. This establishes the `sub` value as the authoritative identifier for the user in Mendix.

{{% alert color="info" %}}
This scenario also applies if you are using Entra ID as IdP. The unique IdP claim `oid` is stored in the `System.User.Name` attribute of the Mendix user entity, the `Name` attribute is configured as the OIDC principal attribute. By mapping the SCIM `externalId` to the `System.User.Name` attribute and configuring `Name` as the SCIM principal attribute enable Mendix to correctly correlate SCIM provisioning.
Copy link

@JaapF JaapF Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we lost a nuance.

it should say:

"...using Entra ID as IdP AND you have mapped the unique idP claim..."

because if the 'and condition' is not met, another scenario applies


#### Transitioning to a Long-Term Standard Identifier (`oid`)

If the organization decides to standardize on `oid` as the long-term unique identifier across both OIDC and SCIM, both configurations must be updated to use this identifier consistently. To implement this change, follow scenario 2 and do the following:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's mention Entra ID again here.
The 'oid' cliam only exists with Entra ID.

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.

3 participants