---
title: Configuring the OAuth client for PingCentral
description: Define a PingCentral-specific OAuth client. These steps explain how to configure PingFederate as the OpenID provider. See Configuring OAuth clients in the PingFederate Server guide for additional information.
component: pingcentral
version: 2.2
page_id: pingcentral:pingcentral_for_iam_administrators:pingcentral_conf_oauth_client
canonical_url: https://docs.pingidentity.com/pingcentral/2.2/pingcentral_for_iam_administrators/pingcentral_conf_oauth_client.html
llms_txt: https://docs.pingidentity.com/pingcentral/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: October 5, 2023
section_ids:
  before-you-begin: Before you begin
  steps: Steps
---

# Configuring the OAuth client for PingCentral

## Before you begin

Define a PingCentral-specific OAuth client *(tooltip: \<div class="paragraph">
\<p>The application in an OAuth framework that requests access to resources. If the request is approved by the authorization server, the client is issued an access token for the resources.\</p>
\</div>)*. These steps explain how to configure PingFederate as the OpenID provider. See [Configuring OAuth clients](https://docs.pingidentity.com/access/sources/dita/topic?resourceid=help_OAuthClientManagementTasklet_OAuthClientManagementState) in the *PingFederate Server* guide for additional information.

## Steps

1. In PingFederate, go to **Applications → OAuth → Clients**.

2. In the **Client ID** field, enter a unique identifier the client provides to the resource server (RS) to identify itself. This identifier is included with every request the client makes.

3. In the **Name** field, enter a descriptive name for the client instance. This name appears when the user is prompted for authorization.

4. In the **Client Authentication** field, select **Client Secret**, and manually enter a secret or click **Generate Secret** to have one created for you.

   You will also use this secret when you configure single sign-on (SSO) *(tooltip: \<div class="paragraph">
   \<p>The process of authenticating an identity (signing on) at one website (usually with a user ID and password) and then accessing resources secured by other domains without reauthenticating.\</p>
   \</div>)* for PingCentral. See [Configuring SSO](pingcentral_conf_sso_pc.html) for details.

5. In the **Redirection URIs** field, enter this URI: `https://<pc-host>:<pc-port>/login/oauth2/code/pingcentral`.

6. Locate the **Allowed Grant Types** field and select **Authorization Code**.

7. **Optional**: If you want API access with bearer tokens, locate the field and select the **Resource Owner Password Credentials** option.

   |   |                                                  |
   | - | ------------------------------------------------ |
   |   | PingCentral doesn't support ID token encryption. |

8. From the **Default Access Token Manager** list, select your access token manager.

9. In the **OpenID Connect** section, from the **ID Token Signing Algorithm** list, select **RSA using SHA-256**. From the **Policy** list, select your OIDC policy.

10. Click **Save**.