---
title: Configuring attribute sources and user lookup for token creation
description: Specify a series of local data stores from which data, along with the attributes supplied in the incoming token, will be used to fulfill the attribute contract.
component: pingfederate
version: 13.1
page_id: pingfederate:administrators_reference_guide:pf_configuring_attribute_sources_user_lookup_token_creation
canonical_url: https://docs.pingidentity.com/pingfederate/13.1/administrators_reference_guide/pf_configuring_attribute_sources_user_lookup_token_creation.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 attribute sources and user lookup for token creation

Specify a series of local data stores from which data, along with the attributes supplied in the incoming token, will be used to fulfill the attribute contract.

## About this task

Attribute sources are specific data store or directory locations containing information that might be needed for the attribute contract. They are used to retrieve supplemental attributes. You can use more than one attribute source when mapping values to the attribute contract. The order matters and affects the queries differently. For example, if you plan on using the result of a query as an input to a subsequent query, stack your attribute sources accordingly.

|   |                                                                                                                                                                                              |
| - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | If you are editing a currently mapped token processor instance, you can add, remove, or reorder attribute sources, which might require additional configuration changes in subsequent tasks. |

## Steps

1. In the **IdP Token Processor Mapping** window, click the **Attribute Sources & User Lookup** tab.

   |   |                                                                                                                                                                                                                                                                                                                                                                                                |
   | - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | The **Attribute Sources & User Lookup** tab is only visible if you selected the **Retrieve Additional Attributes from Data Stores to Fulfill the Attribute Contract** option on the **Attribute Retrieval** tab. For more information, see [Selecting an attribute retrieval method for token creation](help_wstrusttokenprocessormappingtasklet_wstrustselectadditionalattributesstate.html). |

2. Click **Add Attribute Source**.

   ### Result:

   The **Attribute Sources & User Lookup** window configuration opens.

3. On the **Data Store** tab, choose a data store for PingFederate to look up attributes.

4. Enter a description in the **Attribute Source Description** field and a source ID in the **Attribute Source ID** field, if prompted, for the data store.

5. From the **Active Data Store** list, select a data store instance.

   |   |                                                                                                                                                 |
   | - | ----------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | If the data store you want is not shown in the **Active Data Store** list, click **Manage Data Stores** to review or add a data store instance. |

6. Depending on the data store type, the rest of the setup varies as follows.

   **Data store types and their required tasks**

   | Data store type | Required tasks                                                                                                                                                                                                                                                                                 |
   | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   | JDBC            | * [Specifying database tables and columns](pf_specifying_database_tables_columns.html)

   * [Entering a database search filter](pf_entering_database_search_filter.html)                                                                                                                         |
   | LDAP            | - [Specifying directory properties and attributes](pf_specify_directory_properties_and_attributes.html)

   - [Defining encoding for binary attributes](pf_defining_encoding_binary_attributes.html) (optional)

   - [Entering a directory search filter](pf_entering_directory_search_filter.html) |
   | Other           | * [Specifying data source filters and fields](pf_specifying_data_source_filters_fields.html)                                                                                                                                                                                                   |

7. Repeat steps 2 - 6 as needed.

8. Click **Save** to exit the **Attribute Sources & User Lookup** window configuration.