---
title: Configuring local identity fields
description: Configuring local identity fields determines which fields will be displayed as input controls on the user registration and profile management pages.
component: pingfederate
version: 13.1
page_id: pingfederate:administrators_reference_guide:pf_configuring_local_identity_fields
canonical_url: https://docs.pingidentity.com/pingfederate/13.1/administrators_reference_guide/pf_configuring_local_identity_fields.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:
  about-this-task: About this task
  steps: Steps
  result: Result:
---

# Configuring local identity fields

Configuring local identity fields determines which fields will be displayed as input controls on the user registration and profile management pages.

## About this task

When registration is enabled for a local identity profile, select a local identity field to be the unique identifier for the purpose of identifying the users. To enable email ownership verification, add a field to store the email address and another field to store the verification status. While the former can be any field that uses the **Email** or **Text** input control, the latter must use the **Hidden** input control.

## Steps

1. On the **Fields** tab, click **Create New Field**.

2. In the **ID** field, enter a unique identifier. The ID references the field throughout the user interface and is the field name in the HTML template.

3. In the **Label** field, type the field name that users see on the user registration and profile management pages.

4. From the **Type** list, select the type of input control for the field being configured.

5. Under **Applies To**, select one or both options to configure this field to appear on the user registration page, the profile management page, or both. Both options are selected by default.

   This step is applicable only if both **Enable Registration** and **Enable Profile Management** are enabled on the **Profile Info** tab.

6. (Optional) Select the relevant parameters under **Parameters**.

   You can make a non-hidden field required or read-only. You can also configure PingFederate not to record values from this field in logs.

7. (Optional) Enter a value under **Default Value**. Specifying a default value can streamline the registration process. This is the default value of the field unless another value is specified in the authentication policy. For more information, see [Configuring local identity mapping](pf_configuring_local_identity_mapping.html).

   **Default Value** is not shown if you have chosen an input control of **Checkbox group**, **Email**, **Phone**, or **Hidden**, or the **Read-Only** parameter.

8. Add the applicable predefined values under **Options**. This step is applicable and required only if you have chosen **Checkbox Group** or **Dropdown** as the input control.

9. Click **Done**.

   ### Result:

   The administrative console returns to the **Fields** tab.

10. Select the **Unique ID** option for the applicable field. This is applicable and required only if registration is enabled on the **Profile Info** tab.

    |   |                                                                                                                                                                                                                                    |
    | - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
    |   | You cannot choose any field that uses the **Checkbox**, **Checkbox Group**, **Date**, or **Dropdown** input control as a unique identifier, because values from these fields will likely collide as the population of users grows. |

11. Clear the checkbox beside **Strip Leading/Trailing Spaces From the Value of the Unique ID Field** only if you do not want to check for leading and trailing spaces in the unique ID field.

12. Select **Mask All OGNL-Expression Generated Log Values** if you want to mask local identity field values in logs when OGNL expressions might be used to map derived values into outbound single sign-on (SSO) tokens in authentication policies.

13. Click **Next**.