---
title: Configuring LDAP relative DN and object class
description: When a user submits a registration request, PingFederate formulates the distinguished name (DN) of the user by prefixing the relative distinguished name (RDN) to the base DN defined in the LDAP configuration and then asks PingDirectory to create a new account based on the selected object class.
component: pingfederate
version: 13.1
page_id: pingfederate:administrators_reference_guide:pf_configuring_ldap_relative_dn_object_class
canonical_url: https://docs.pingidentity.com/pingfederate/13.1/administrators_reference_guide/pf_configuring_ldap_relative_dn_object_class.html
llms_txt: https://docs.pingidentity.com/pingfederate/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: July 10, 2024
section_ids:
  steps: Steps
  related-links: Related links
---

# Configuring LDAP relative DN and object class

When a user submits a registration request, PingFederate formulates the distinguished name (DN) of the user by prefixing the relative distinguished name (RDN) to the base DN defined in the LDAP configuration and then asks PingDirectory to create a new account based on the selected object class.

## Steps

1. (Optional) Click **View List of Available LDAP Attributes** to determine which LDAP attributes can be used to construct the RDN pattern.

2. In the **Relative DN Pattern** field, enter a valid pattern.

   The pattern is as follows.

   `[.parmname]`attribute1`=value1…​, [.parmname]`attributeN`=valueN]`

   If you want to use the *${entryUUID}* variable to guarantee the uniqueness of the relative DNs for all users, you must use it with the `entryUUID` LDAP attribute, such as in the following example.

   `entryUUID=${entryUUID}`

3. From the **Object Class** list, select the primary objectClass value used when creating a new local identity profile; for example, inetOrgPerson.

4. (Optional) From the **Auxiliary Object Class Name** list, select an objectClass that contains additional required attributes that are not available in the primary objectClass, and click **Add**. You can add multiple object classes as needed. For example, if you require the placeOfBirth attribute for a user's profile, you can add the naturalPerson root object class to the **Auxiliary Object Class Name** list. Doing this requires that you have done the following:

   1. Added placeOfBirth as a field on the **Fields** tab when configuring the local identity profile.

   2. Added the naturalPerson root object class and placeOfBirth attribute on the **LDAP Configuration** tab when configuring the datastore.

5. Click **Next**.

## Related links

* [Managing entries](https://docs.pingidentity.com/pingdirectory/10.3/pingdirectory_server_administration_guide/pd_ds_manage_entries.html)