--- title: Identify a SCIM resource at the destination description: When a System for Cross-domain Identity Management (SCIM) Sync Destination needs to synchronize a change to a SCIM resource on the destination SCIM server, it must first fetch the destination resource. If the destination resource ID is known, the resource will be retrieved by its ID. If not, a search is performed using the mapped destination correlation attributes. Configuring this requires coordination between the Sync Class and the scim-resources.xml mapping file. component: pingdirectory version: 11.0 page_id: pingdirectory:pingdatasync_server_administration_guide:pd_sync_identify_scim_resource_dest canonical_url: https://docs.pingidentity.com/pingdirectory/11.0/pingdatasync_server_administration_guide/pd_sync_identify_scim_resource_dest.html revdate: September 13, 2023 --- # Identify a SCIM resource at the destination When a System for Cross-domain Identity Management (SCIM) *(tooltip: \
\

An application-level, HTTP-based protocol for provisioning and managing user identity information. SCIM supplies a common schema for representing users and groups and provides a REST API.\

\
)* Sync Destination needs to synchronize a change to a SCIM resource on the destination SCIM server, it must first fetch the destination resource. If the destination resource ID is known, the resource will be retrieved by its ID. If not, a search is performed using the mapped destination correlation attributes. Configuring this requires coordination between the Sync Class and the `scim-resources.xml` mapping file. The `scim-resources.xml` mapping file treats the value of the `` element's `ldapAttribute` attribute as the SCIM ID of the source entry. If this value is also listed as a value of the Sync Class's `destination-correlation-attributes` property, then the value of this Lightweight Directory Access Protocol (LDAP) *(tooltip: \
\

An open, cross platform protocol used for interacting with directory services.\

\
)* attribute is used as the SCIM ID of the destination resource. If no value of `destination-correlation-attributes` matches the `` element's `ldapAttribute` attribute, the SCIM ID of the destination resource is considered unknown. In this case, the SCIM Sync Destination treats the values of `destination-correlation-attributes` as search terms, using them to construct a filter for finding the destination resource. Each value of `destination-correlation-attributes` will be mapped to a corresponding SCIM attribute name, and equality matches will be used in the resulting filter. If the `ldapAttribute` value is not listed as a destination correlation attribute, this setting is not used by PingDataSync. The following table illustrates an `LDAPSearch` element that contains a `resourceIDMapping` element: **Identifying a SCIM resource** | Method for retrieving SCIM resource | Condition | Example condition | Example request | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | | Retrieve resource directly | Used if a `destination- correlation-attribute` value matches the ` ldapAttribute` value. | `destination-correlation- attribute=mail,uid;` | `GET scim/Users/ person@example.com` | | Retrieve resource using search | Used if no `destination- correlation- attribute`value matches the ` ldapAttribute` value. | `destination-correlation-attribute=mail,uid;` | `GET /scim/Users? filter=emails+eq+"person@example.com" and+userName+eq"person"` | The unique ID of a destination SCIM resource will most likely be unknown, and the search method will need to be used. However, not all SCIM service providers support the use of filters. Therefore, not all SCIM service providers might be usable as SCIM Sync Destinations.