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.

  1. Copy and rename the sample.template.txt file located in the <pf_install>/pingfederate/server/default/conf/template/ldap-templates directory.
  2. Change the template.name property value in the new template file.
    This property value appears in the LDAP Type list on the LDAP Configuration screen when you save the template.
  3. Modify other property values in the file to match the corresponding configuration of your directory server.
    These properties correspond to the fields shown on the Outbound Provisioning > Channel > Source Settings screen. They help the provisioner to determine when user records are added, changed, or removed.
  4. 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.

Once configured, you may create a new LDAP datastore using the newly defined LDAP type. To streamline outbound provisioning configuration, select the LDAP datastore that uses the newly defined LDAP type on the Source screen.