PingOne provisioning propagates user identity information from the PingOne directory to a target identity store, or from a source identity store to the PingOne directory.
The provisioning service continually synchronizes changes to and from the source and target identity stores. Provisioning events are triggered by any addition, change, or deletion of users or user information in the source identity store.
How do I use it?
You’ll create a connection that defines the source or target identity store for identities. You can then set up rules to define which identities from the source identity store are provisioned. Rules define which users are provisioned and how attributes are mapped between the source identity store and the target identity store.
- Source. The connection to the source identity store.
- Target. The connection to the target identity store.
- Filter. Determine which identities are provisioned, based on factors such as population or user attributes.
- Attribute mapping. Map attributes from one identity store to another.