The Attribute Mapping screen provides a means of managing how attributes from your user store are mapped to SCIM attributes in the core schema and custom attributes through a schema extension or to the provisioning fields supported for your organization's SaaS-customer account.

Attribute Mapping

If you are provisioning for SCIM, your SP may make one or more optional core attributes mandatory. Refer to the SCIM documentation from the SP or the SCIM Resource Schema representation.


For non-SCIM SaaS connectors, PingFederate automatically retrieves from the vendor the Field Names shown on this screen, but only on the first pass through the screen flow. If you are using this screen to modify an existing mapping configuration, click Refresh Fields near the bottom of the screen to synchronize the list with the target if needed.

For each field, the Specify Attribute Mapping screen provides a means of adding or modifying the mapping details.


All required attributes listed in the Field Name column, indicated with asterisks, must be mapped. Click View Partner Field Specifications near the of the screen for a summary of requirements for all fields specified for the target partner.

For some fields, PingFederate preselects LDAP attributes commonly used to store the required values.

  1. Click Edit under Action for a field.

    If you have specified any custom attributes, they are listed at the end of the Attribute Mapping screen.

  2. On the Specify Attribute Mapping screen, provide mapping details.
  3. Repeat for each attribute shown in the Field Name column as needed.

    For most fields, if you need to map more than one attribute from your datastore into a single field at the target location, then you must use an OGNL expression to indicate how the attribute values are to be combined.

    The only exception is a field called LDAP Attributes Map, provided primarily to support SCIM attributes specific to PingOne® for Enterprise. This field may contain multiple attributes without using OGNL.

  4. Click Next.