Setting up PingDirectory for customer identities - PingFederate - 11.2

PingFederate Server

bundle
pingfederate-112
ft:publication_title
PingFederate Server
Product_Version_ce
PingFederate 11.2
category
Administrator
Administratorguide
Audience
Capability
ContentType
DeploymentMethod
Guide
Product
Productdocumentation
SingleSignonSSO
Software
SystemAdministrator
pf-112
pingfederate
ContentType_ce
Guide
Guide > Administrator Guide
Product documentation

PingFederate can optionally store customer identities in PingDirectory. After you have installed PingDirectory, update the LDAP schema with a new object class and a couple attributes to store customer identities and their connections.

Update the LDAP schema with a new object class and a couple attributes using an LDIF file provided. To optimize performance, apply updates in indexes to the directory as well. In addition, you must configure in PingFederate an LDAP datastore connection to your PingDirectory and an LDAP Username password credential validator (PCV)password credential validator (PCV)PCV Configures a centralized location for user credential validation. The validator instances can then be referenced by PingFederate instance for the HTML Form Adapter to validate user credentials. If you have previously created these components, you can reuse them.

Note:

Skip this configuration if your use case does not involve registration or profile management. For more information, see Enabling third-party identity providers without registration.

  1. Update the LDAP schema.
    1. Sign on to the PingDirectory administrative console.
    2. Go to the LDAP Schema > Schema Utilities screen.
    3. Click Import Schema Element.
    4. Copy the schema changes from the <pf_install>/pingfederate/server/default/conf/local-identity/ldif-scripts/local-identity-pingdirectory.ldif file and paste them into the text area.
      If you are creating a new organizational unit as part of the LDIF import, edit the DN information.
    5. Click Import.
  2. Create an equality index for the pf-connected-identity attribute.

    Use PingDirectory's dsconfig utility to create this index. The dsconfig utility is interactive. You can also provide inputs as command arguments. For example, the following samples create the pf-connected-identity index.

    $ bin/dsconfig create-local-db-index \
                      --backend-name userRoot \
                      --index-name pf-connected-identity \
                      --set index-type:equality

    After adding the index, use the rebuild-index utility to build the indexes. For instance, the following sample builds the required index.

    $ bin/rebuild-index \
                               --baseDN "dc=example,dc=com" \
                               --index pf-connected-identity
  3. Create an LDAP datastore connection to your PingDirectory on System > Data Stores.

    If you have already created an LDAP datastore connection to your PingDirectory, you can reuse it.

  4. Create an instance of the LDAP Username PCV on System > Password Credential Validators to validate user credentials stored in PingDirectory.

    If you have already created an LDAP Username PCV instance, you can reuse it.

    Note:

    Later you will create a local identity profile as part of the customer IAM configuration. The Search Base value here should match the Base DN value defined in the local identity profile. For more information, see Configuring LDAP base DN and attributes.

  5. For the local identity profile management page to work correctly, enable PingDirectory's ds-pwp-state-json virtual attribute.

    Use PingDirectory's dsconfig utility and a command like the following to enable the ds-pwp-state-json virtual attribute for users with the object class person:

    dsconfig set-virtual-attribute-prop \
       --name "Password Policy State JSON" \
       --set enabled:true \
       --set require-explicit-request-by-name:true \
       --set "filter:(objectClass=person)"