This section describes limitations and other constraints to consider when synchronizing changes to a PingOne environment.


All PingOne user resources must exist within a population. The PingOne synchronization destination provides the following methods for managing a user's population:

  • If a single population is in use, set the configuration attribute default-population-id on the sync destination.
  • If multiple populations are in use, use a constructed attribute mapping.

The following syntax provides an example.

dsconfig create-attribute-mapping \
   --map-name PingDirectory_to_PingOne_User_Map  \
   --mapping-name population  \
   --type constructed  \
   --set 'value-pattern:{{"id":"[DEFAULT_POPULATION_ID]"}}'

To set the population properly, make certain to construct a valid JSON object.