From cdebc46cd1cf23fd563f5e529d560e95b8fd71ed Mon Sep 17 00:00:00 2001 From: Nikos Polykandriotis Date: Tue, 17 Dec 2024 17:00:03 +0200 Subject: [PATCH] fix: Update create enterprise OIDC label --- .../enterprise-connections/oidc/custom-provider.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/authentication/enterprise-connections/oidc/custom-provider.mdx b/docs/authentication/enterprise-connections/oidc/custom-provider.mdx index ffe342ec81..9079a542d2 100644 --- a/docs/authentication/enterprise-connections/oidc/custom-provider.mdx +++ b/docs/authentication/enterprise-connections/oidc/custom-provider.mdx @@ -29,7 +29,7 @@ To make the setup process easier, it's recommended to keep two browser tabs open 1. In the Clerk Dashboard, navigate to the [**SSO Connections**](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections) page. 1. Select **Add connection** and select **For specific domains**. - 1. Under **Third party**, select **OpenID Connect (OIDC)**. + 1. Under **OpenID Connect (OIDC)**, select **Custom OIDC Provider**. 1. Add the **Name** of the connection. 1. Add the **Key** of the provider. This is the provider's unique identifier (cannot be changed after creation). 1. Add the **Specific Domain** that you want to allow this connection for. This is the domain of the users you want to allow to sign in to your app.