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, administrators should
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 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 cannot modify the values of those attributes.