<commit_before>---
connection: Auth0 OpenIDConnect
seo_alias: auth0-oidc
image: /media/connections/auth0.png
description: You can use a Client on another Auth0 tenant as an OIDC identity provider in your current Auth0 tenant.
toc: true
---

# Authenticate using OpenIDConnect to another Auth0 Tenant

You can use a client on another Auth0 tenant (referred to below as the **OIDC Provider tenant**) as an identity provider in your current Auth0 tenant (the **Relying Party tenant**).

## Configure the OIDC Provider Auth0 Tenant

1. Create a Client or edit an existing one.
2. Take note of its **clientID** and **clientSecret**. You will need these to create the connection in the Relying Party tenant.
3. Add the Relying Party tenant's login callback to the list of **Allowed Callback URLs**: `https://${account.namespace}/login/callback`

![](/media/articles/connections/social/auth0-oidc/child-app.png)

## Configure the Relying Party Auth0 Tenant

The Auth0-to-Auth0 connection is not yet supported in the Dashboard. You need to create the connection using the [Create a connection](/api/v2#!/Connections/post_connections) endpoint, which will require an [Management API V2 token](/api/management/v2/tokens) with `create:connections` scope.

Here is a sample request:

```sh
curl -H "Content-Type: application/json" -H 'Authorization: Bearer {YOUR_API_V2_TOKEN}' -d @auth0-oidc-connection.json https://${account.namespace}/api/v2/connections
```

with the **auth-oidc-connection.json** file containing:

```js
{
  "name": "YOUR-AUTH0-CONNECTION-NAME",<commit_msg>Revised instructions for the OIDC Provider setup<commit_after>---
connection: Auth0 OpenIDConnect
seo_alias: auth0-oidc
image: /media/connections/auth0.png
description: You can use a Client on another Auth0 tenant as an OIDC identity provider in your current Auth0 tenant.
toc: true
---

# Authenticate using OpenIDConnect to another Auth0 Tenant

You can use a client on another Auth0 tenant (referred to below as the **OIDC Provider tenant**) as an identity provider in your current Auth0 tenant (the **Relying Party tenant**).

## Configure the OIDC Provider Auth0 Tenant

1. Create a Client or edit an existing one. Set the client type to regular web app.
2. Take note of its **clientID** and **clientSecret**. You will need these to create the connection in the Relying Party tenant.
3. Add the Relying Party tenant's login callback to the list of **Allowed Callback URLs**: `https://${account.namespace}/login/callback`

![](/media/articles/connections/social/auth0-oidc/child-app.png)

4. Ensure that the **OIDC-Conformant** toggle in the **OAuth** tab under the client's **Advance Settings** is turned **off**.

::: note
The requirement for the **OIDC-Conformant** toggle to be **off** is a temporary requirement that will be removed in the future.
:::

## Configure the Relying Party Auth0 Tenant

The Auth0-to-Auth0 connection is not yet supported in the Dashboard. You need to create the connection using the [Create a connection](/api/v2#!/Connections/post_connections) endpoint, which will require an [Management API V2 token](/api/management/v2/tokens) with `create:connections` scope.

Here is a sample request:

```sh
curl -H "Content-Type: application/json" -H 'Authorization: Bearer {YOUR_API_V2_TOKEN}' -d @auth0-oidc-connection.json https://${account.namespace}/api/v2/connections
```

with the **auth-oidc-connection.json** file containing:

```js
{
  "name": "YOUR-AUTH0-CONNECTION-NAME",
{'fraction_non_alphanumeric': 0.10500575373993096, 'fraction_numerical': 0.013521288837744535, 'mean_word_length': 4.81438127090301, 'pattern_counts': {'":': 2, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2876910', 'n_tokens_mistral': 1047, 'n_tokens_neox': 1007, 'n_words': 420}