Creating an outbound rule for a connection through an LDAP gateway - PingOne - PingOne Cloud Platform

PingOne Cloud Platform

bundle
pingone
ft:publication_title
PingOne Cloud Platform
Product_Version_ce
PingOne
PingOne Cloud Platform
category
Administratorguide
ContentType
Guide
Product
Productdocumentation
p1
p1cloudplatform
ContentType_ce
Guide
Guide > Administrator Guide
Product documentation

Create a rule to define which users are provisioned and how attributes are mapped between PingOne and the LDAP directory.

  • The RDN attribute that specifies the relative portion of the DN (distinguished name), which uniquely identifies the user in the LDAP directory.
  • The Base DN that specifies where the users will be created in the LDAP directory.
  1. Go to Integrations > Provisioning.
  2. Click + and then click New rule.
  3. Enter a name and description for the rule. The rule name will appear in the list when you've completed and saved the rule.
  4. Click Create rule.
  5. Click the Target button, and then click the + icon for the appropriate gateway to add it as the target connection. PingOne Directory will be automatically added as the source.
    Note:

    If you haven’t created the appropriate connection yet, see Creating an LDAP gateway provisioning connection. You can add disabled connections to a source or target, but the connection must be enabled to enable an associated rule.

  6. Enter the following:
    • RDN attribute. Select the PingOne attribute that will map to the RDN attribute. The RDN attribute is the relative portion of the DN (distinguished name) that uniquely identifies the user in the LDAP directory
      Note:
      The default attributes are based on the directory type of the gateway used.
      • For Active Directory, RDN defaults to cn.

        For Ping Directory, RDN defaults to uid.

    • Base DN. Specifies the location in the LDAP directory structure where users will be created. For more information, see Distinguished Names in the Microsoft LDAP documentation.

  7. Click Save.

Adding attribute mapping for outbound provisioning