---
title: Selecting a request contract
description: Select a request contract to be used to map attribute values into the security token.
component: pingfederate
version: 13.1
page_id: pingfederate:administrators_reference_guide:help_wstrustsettingstasklet_wstrustmanagerequestcontractsstate
canonical_url: https://docs.pingidentity.com/pingfederate/13.1/administrators_reference_guide/help_wstrustsettingstasklet_wstrustmanagerequestcontractsstate.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 5, 2022
section_ids:
  about-this-task: About this task
  steps: Steps
---

# Selecting a request contract

Select a request contract to be used to map attribute values into the security token.

## About this task

This optional setting allows you to use XML parameters contained in RSTs for token-attribute mapping. For more information, see [Managing STS request parameters](pf_managing_sts_request_parameters.html). If you are not using request parameters, click **Next** to continue.

|   |                                                                                                                                                                                                       |
| - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | If you are editing an existing configuration, you can change the request contract or disable this optional setting. These changes night require additional configuration changes in subsequent tasks. |

## Steps

1. To use request parameters, select the **Request Contract** checkbox to access the **Request Contract**list.

2. Select a request contract from the **Request Contract** list.

   If the contract you want is in the **Request Contract** list, click **Manage STS Request Parameters**.

   When selected, you can choose the request contract as the attribute source in the **IdP Token Processor Mapping** configuration later in the setup.

3. Click **Next**.