You may need to map one or more resource attributes to attributes in the LDAP sources you have defined in your LDAP container. You may need to do this because the business process does not have direct access to the attributes in the LDAP sources, but it does have access to the resource attributes in the organization model.
When you map a resource attribute to an LDAP attribute, it gives the business process access to the data in the LDAP attribute at runtime.1
The following diagram shows an example of how you can map resource attributes to LDAP attributes.
Mapping Resource Attributes to LDAP Attributes
Procedure
Call
getOrgModel to get details about the entities in an organization model.
The request identifies the major version number of the organization model, which can be obtained using the
listOrgModelVersions function.
The response from the
getOrgModel function provides GUIDs for all entities in the organization model, including resource attributes defined in the model.
Call
listContainers to retrieve the LDAP containers to which you (the calling user) have access.
The response from
listContainers provides
ldap-alias and
ldap-query, which you will need to request the list of attributes from the LDAP source.
Call
listAttributeNames to list the LDAP attributes in the identified LDAP source.
Call
saveContainer to specify which resource attributes to map to named LDAP attributes.
The
saveContainer function response indicates success by returning the container identifier.
1 Note that resource attributes of type "Enum" and "EnumSet" cannot be mapped to LDAP attributes.