The PingOne LDAP Gateway reduces the complexity of moving to the cloud while maintaining connectivity to on-premise end-user data.
Make sure you have the following in place:
- A PingOne environment configured with an LDAP gateway. See Gateways and Adding a Gateway.
- A connection between PingFederate and PingOne. See Creating connections to PingOne.
When PingFederate is deployed off-premise, as a PingOne Advanced Service or in your own cloud deployment, you can configure the PingOne LDAP Gateway datastore to enable PingFederate to access an on-premise LDAP directory for HTML Form Adapter functionality, provisioning, customer identity access management (CIAM), and other areas.
Currently, you cannot use the PingOne LDAP Gateway for grant storage, persistent authentication sessions, and OAuth client records. All other LDAP datastore functionality works in the same way as the direct LDAP datastore.