Use Clerk as an OAuth 2 Provider

Clerk can be configured as an identity provider to facilitate Single Sign-On (SSO) with other clients that support the OAuth 2.0 protocol. With this feature, your users can sign in with your Clerk application on other websites to authorize sharing of their user info.

Clerk IDP Flow

Retrieve callback URL from the client application

Retrieve the Callback URL for the client application you want to configure. This is where your users will be redirected to after a successful authentication and is required to successfully create your OAuth application in the next step.

Create an OAuth application in Clerk

Next, you need to create an OAuth Application in Clerk via the Backend API by providing the Callback URL and a Name. Note that in this context the name is used to help you identify your application and is not displayed anywhere publicly.

POST /v1/oauth_applications
 -X POST \
 -H "Authorization: Bearer <CLERK_SECRET_KEY>"  \
 -H "Content-Type: application/json" \
 -d {"callback_url":"", "name": "oauth_app_1", "scopes": "profile email"}

To create an OAuth Application that uses the authorization code flow with proof of key exchange (PKCE), set public to true in the POST request body.

{"callback_url":"", "name": "oauth_app_pkce", "public": true}

Clerk creates an OAuth application and returns it's configurations back to you.

    "scopes":"profile email",


For security reasons, Clerk does not store your Client Secret and cannot show it to you again, so we recommend you download the secret and store it someplace secure.

Configure OAuth application in client

Now that you have set up an OAuth application in Clerk, you will need to configure these settings in your Client.

  • Client ID: Public identifier of your OAuth application
  • Client Secret: Confidential secret used to authenticate your OAuth application
  • Authorization URL: Used by the Client to request authorization from your user
  • Token URL: Used by the Client to retrieve access tokens
  • Scopes: OAuth scopes used to grant access to the Client. Clerk supports profile, email, public_metadata, and private_metadata. The metadata scopes ensure that the user info endpoint returns the user's public, private and unsafe metadata.
  • User Info URL: Used by the Client to retrieve the email address and profile (username, first and last name) associated to your user

Below is an example of a response from /oauth/userinfo.

    "object": "oauth_user_info",
    "instance_id": "ins_2O4Ak02T4fDmKKv6tK5h0WJ8ou8",
    "email": "",
    "email_verified": true,
    "family_name": "first_name",
    "given_name": "last_name",
    "name": "first_name last_name",
    "username": "my_username",
    "picture": "https://profile_image_public_url/img.png",
    "user_id": "my_user_id",
    "public_metadata": {},
    "private_metadata": {},
    "unsafe_metadata": {}

Frequently asked questions (FAQ)

How can the access tokens obtained from the Token URL be used?

Access tokens retrieved from the Token URL are used in the Authorization header when the OAuth2 client retrieves user information from the /oauth/userinfo endpoint. They are not the same as Clerk's JWT session tokens.

When do the tokens expire?

Access tokens expire after 2 hours, and refresh tokens expire after 3 days.

Is OpenID Connect supported?

At this time, OIDC is not supported.


What did you think of this content?