The following example shows how to add a correlated LDAP data view to a LDAP Mapping SCIM Resource Type on a PingDirectory server. The SCIM Resource Type will be a user, and the correlated LDAP data view will allow access to a document that matches their user ID.
In this example, a new PingDirectory server is set up
using custom sample data. When configuring the correlation, it is encouraged for
administrators to use attributes that are inherently either immutable or
non-volatile, such as uid
or entryUUID
. This
prevents errors produced by a conflict between the values of primary and secondary
correlation attributes.
Administrators can also make the correlation SCIM attributes immutable by setting the --set mutability:read-only property when defining an attribute in the SCIM schema configuration. That way, SCIM requests will not be able to modify the values of those attributes.