The PingOne User model contains simple JSON attributes like "title": "Director" as well as complex JSON objects like {"name": {"given": "Jane", "family": “Doe”}}. To ensure accurate processing when you construct attribute mappings that interact with complex objects, construct valid JSON strings and use the command jsonEscape, as the following example shows.

dsconfig create-attribute-mapping \
   --map-name PingDirectory_to_PingOne_User_Map  \
   --mapping-name name  \
   --type constructed  \
   --set 'value-pattern:{{"given":"{givenname:jsonEscape}","family":"

Some attributes in the User resource are operational and cannot be modified by synchronizing data. For more information, refer to the PingOne for Customers API Guide.

Correlating entries

The PingOne User Resource model provides an attribute named externalId. To ensure that users correlate to the appropriate entry in PingDirectory, map entryUUID to this value and configure externalId as a destination-correlation-attribute on the Sync class.