Defining a custom LDAP type for outbound provisioning - PingFederate

Defining a custom LDAP type for outbound provisioning - PingFederate - 10.1

PingFederate Server

bundle

pingfederate-101

ft:publication_title

PingFederate Server

Product_Version_ce

PingFederate 10.1

category

Product

pf-101

pingfederate

ContentType_ce

Page created: 21 Jan 2020 |

Page updated: 15 Jul 2020

| 1 min read

10.1 PingFederate Product Configuration User task Administrator Audience Software Deployment Method LDAP Standards, specifications, and protocols Product documentation Content Type

If you are using outbound provisioning and your directory server is not PingDirectory, Microsoft Active Directory, Oracle Unified Directory, or Oracle Directory Server, you can define a custom LDAP type for PingFederate to use to streamline the provisioning configuration.

Copy and rename <pf_install>/pingfederate/server/default/conf/template/ldap-templates/sample.template.txt file.
Change the template.name property value in the new template file.
This property value appears in the LDAP Type list on the LDAP Configuration window when you save the template.
Modify other property values in the file to match the corresponding configuration of your directory server.
These properties correspond to the fields shown on Outbound Provisioning > Channel > Source Settings. They help the provisioner determine when user records are added, changed, or removed.
Save the new template file.
For a clustered PingFederate environment, perform these steps on the console node. No changes or restart of the PingFederate service is required on any nodes.

After you have configured the LDAP type, you can create a new LDAP datastore using the newly defined LDAP type. To streamline outbound provisioning configuration, select the LDAP data store that uses the newly-defined LDAP type in the Source window.