Identity Propagation
PingOne can propagate user identity information from the PingOne directory to a target identity store, or from a source identity store to the PingOne directory. The service continually synchronizes changes to and from the source and target identity stores. Propagation events are triggered by any addition, change, or deletion of users or user information in the source identity store.
These tasks show you how to use the platform APIs to perform common actions for managing identity propagations. Identity propagation use cases often call the following platform API resources:
| Platform API | Description |
|---|---|
The propagation plans service implements unidirectional provisioning relationships between pairs of identity stores. |
|
The propagation stores service implements connections to an identity store owned by a customer. |
|
The propagation rules service implements unidirectional provisioning relationships between a subset of identities on a source identity store and a target identity store. |
|
The propagation mappings service implements attribute mappings associated with identity propagation rules. |
Refer to Provisioning for more information regarding propagation of identities and Inbound and outbound provisioning for more information regarding inbound versus outbound identity stores.