You can use some connection types for outbound provisioning, some for inbound provisioning, and some for both.
For outbound provisioning, identities flow from PingOne to an external identity store. PingOne is the source and the external identity store is the target. For outbound provisioning, changes are near real-time. When there is a change to a user in PingOne, the target identity store is updated immediately.
For inbound provisioning, identities flow from an external identity store to PingOne. The external identity store is the source and PingOne is the target.
For inbound provisioning with the Workday provisioner, a polling mechanism checks the source identity store every 15 minutes. This value is not configurable. After five consecutive polling failures, the polling mechanism will time out with a warning. At this point, you can check your configuration and try again. The timeout expires after 12 hours, at which time the polling mechanism will attempt to run a full re-sync for the associated provisioning rule.
We recommend that you use the SCIM provisioning connection for outbound provisioning only. For importing identities into PingOne, use the SCIM Users API. For more information, see Using the SCIM API to import users.
PingOne must be either the source or target identity store.
Identity store |
Inbound |
Outbound |
---|---|---|
SCIM |
We recommend that you use the PingOne API to set up inbound SCIM for user provisioning. For more information, see SCIM in the PingOne API Reference. |
Yes |
Salesforce |
Yes |
|
Salesforce Communities |
Yes |
|
Salesforce Leads and Contacts |
Yes |
|
Aquera |
Yes |
|
Workday |
Yes Note:
Users are retrieved from the source identity store using a polling mechanism, which checks the source identity store every 15 minutes. |
Yes |
Microsoft Azure (Office 365) |
Yes |
|
Zoom |
Yes |
|
Slack |
Yes |
|
ServiceNow |
Yes |
|
Google Workspace |
Yes |
|
GitHub EMU |
Yes |
|
LDAP Gateway |
Yes |
Yes |