Skip to content

Commit 80e0de2

Browse files
committed
Small fix
1 parent a31530a commit 80e0de2

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎content/en/docs/deployment/general/subscription-management/user-metering/implementing-user-metering.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ User identification strategies can vary across application portfolios, particula
4040

4141
* Handling Case Sensitivity: When using email addresses or other text-based identifiers, always store these values in lowercase to prevent metering issues caused by case sensitivity. The `system.user.name` attribute is case-sensitive by design. Mendix's standard SAML, OIDC SSO, and SCIM modules already apply this for email claims received from Identity Providers (IdPs).
4242

43-
3. Address pairwise identifiers (for example, OIDC `sub` claim): Some identity providers, such as Microsoft Entra ID, generate "pairwise" identifiers (for example, Entra ID's `sub` claim). These identifiers are unique for each application for the same user. This is designed to prevent correlation across different service providers. However, you are using this technical identifier as the global unique identifier for user metering, it can lead to incorrect multi-app metering within your portfolio. When using the OIDC SSO module with Microsoft Entra ID, you can use the `oid` claim instead of the `sub` claim as the global unique identifier. The `oid` claim contains the Entra ID user object ID and remains consistent for the same user across all applications. Alternatively, if you follow the recommended approach of using the user’s email address as the global unique identifier for user metering, pairwise identifiers will not impact your metering accuracy.
43+
3. Address pairwise identifiers (for example, OIDC `sub` claim): Some identity providers, such as Microsoft Entra ID, generate pairwise identifiers (for example, Entra ID's `sub` claim). These identifiers are unique for each application for the same user. This is designed to prevent correlation across different service providers. However, you are using this technical identifier as the global unique identifier for user metering, it can lead to incorrect multi-app metering within your portfolio. When using the OIDC SSO module with Microsoft Entra ID, you can use the `oid` claim instead of the `sub` claim as the global unique identifier. The `oid` claim contains the Entra ID user object ID and remains consistent for the same user across all applications. Alternatively, if you follow the recommended approach of using the user’s email address as the global unique identifier for user metering, pairwise identifiers will not impact your metering accuracy.
4444

4545
4. Integrating with existing application logic: If your current applications use varying `system.user.name` values or different provisioning methods, you can implement `UserCommons.namedUserIdentifier.value` without altering existing logic. Continue using your existing application logic for `system.user.name` if necessary, but additionally implement logic to populate `UserCommons.namedUserIdentifier.value` with your chosen consistent cross-app identifier (for example, email address or `oid` claim). This ensures the metering mechanism has a reliable, consistent identifier to use. If your applications are already consistently storing the same identifier for a multi-app user in `system.user.name`, you do not have to use the `UserCommons.namedUserIdentifier.value`.
4646

0 commit comments

Comments
 (0)