---
title: Configuring other OIDC identity providers
description: Learn how to configure an OIDC provider as the identity provider for Delegated Admin.
component: pingdirectory
version: 11.0
page_id: pingdirectory:delegated_admin_application_guide:pd_da_config_oidc_idp
canonical_url: https://docs.pingidentity.com/pingdirectory/11.0/delegated_admin_application_guide/pd_da_config_oidc_idp.html
section_ids:
  steps: Steps
  next-steps: Next steps
---

# Configuring other OIDC identity providers

Complete the following steps to configure a non-PingFederate OpenID Connect (OIDC) *(tooltip: \<div class="paragraph">
\<p>An authentication protocol built on top of OAuth that authenticates users and enables clients (relying parties) of all types to request and receive information about authenticated sessions and users. OIDC is extensible, allowing clients to use optional features such as encryption of identity data, discovery of OpenID Providers (OAuth authorization servers), and session management.\</p>
\</div>)* provider as the identity provider for Delegated Admin.

## Steps

1. Create an OIDC client and specify the following values:

   * **Redirect URI**: http\://*\<hostname:port>*/delegator/

     This is the server that hosts the Delegated Admin web application. Your OIDC client might also call this value **Redirect URL**, **Callback URI**, or **Callback URL**.

   * **Scopes**: urn:pingidentity:directory-delegated-admin

   * **Grant type**: Authorization code

   * **PKCE enforcement**: Required

   * **Token endpoint authentication method**: None

2. Make a note of the following OIDC client values, which are required to install Delegated Admin:

   * **Client ID**

   * **OIDC authority URL**

     This value represents the base URL of the OIDC client's Discovery endpoint. Your OIDC provider might use a different name for this URL.

## Next steps

After installing Delegated Admin, configure [PingDirectory to use the OIDC provider as the identity provider](pd_da_config_oidc_pd.html).