Resource schemas

ISAM supports the following resource schemas from RFC 7643.

SVA also provides the following extensions to the “User” Resource Schema:

Data in the ISAM schemas can be managed for users that do not necessarily exist in the LDAP user registry. For instance, scenarios where a user logged in with their identity from another provider.

Consider a user logging in with an identity from social.ibm.com. Their AZN_CRED_PRINCIPAL_NAME is https://social.ibm.com/myTestUser. The SCIM interface can be used to manage data on the ISAM extension schemas if the correct SCIM user ID is provided.

The SCIM user ID expected by the SCIM application is the Base64 and URL encoded version of the username, which in this case is “aHR0cHM6Ly9zb2NpYWwuaWJtLmNvbS9teVRlc3RVc2Vy”. Even though the user does not exist in the LDAP user registry and has no attributes in the defined User Resource Schema, it is still possible to manage their data in the ISAM specific schemas.

In the following example, a user is not in the user registry but still has MMFA Authenticators data.

Parent topic: User Self-Care with the SCIM API