Skip to content

Commit

Permalink
finish
Browse files Browse the repository at this point in the history
  • Loading branch information
victoriaxyz committed Nov 1, 2024
1 parent 13179a5 commit d35062d
Showing 1 changed file with 9 additions and 8 deletions.
17 changes: 9 additions & 8 deletions docs/authentication/social-connections/gitlab.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ description: Learn how to allow users to sign up and sign in to your Clerk app w
- Use GitLab to authenticate users with OAuth
</TutorialHero>

Enabling OAuth with [GitLab](https://about.gitlab.com) allows your users to sign up and sign in to your Clerk app with their GitLab account.
Enabling OAuth with [GitLab](https://docs.gitlab.com/ee/integration/oauth_provider.html) allows your users to sign up and sign in to your Clerk app with their GitLab account.

## Configure for your development instance

Expand All @@ -35,7 +35,7 @@ For _development instances_, Clerk uses preconfigured shared OAuth credentials a

For _production instances_, you must provide custom credentials which involves generating your own **Client ID** and **Client Secret** using your GitLab account.

To make the setup process easier, it's recommended to keep two browser tabs open: one for your [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections) and one for your [GitLab's Developer Portal](https://developer.gitlab.com).
To make the setup process easier, it's recommended to keep two browser tabs open: one for your [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections) and one for your [GitLab](https://gitlab.com) account.

<Steps>
### Enable GitLab as a social connection in Clerk
Expand All @@ -48,15 +48,16 @@ To make the setup process easier, it's recommended to keep two browser tabs open

### Create a GitLab app

1. In the GitLab Developer Portal, navigate to the [**Your Apps**](https://api.slack.com/apps) page and select **Create an App**.
1. A modal will open. Depending on your app needs, select either **From a manifest** for **From scratch**. For more information on which to choose, refer to [GitLab's doc on manifests](https://api.slack.com/reference/manifests).
1. After following the respective steps for either option, you'll be redirected to the **App Credentials** page. Save the **Client ID** and **Client Secret** somewhere secure. Keep this page open.
1. In the sidebar, navigate to the **OAuth & Permissions** page.
1. Scroll down to the **Redirect URLs** section and paste the **Redirect URI** you saved from the Clerk Dashboard. Select **Add**, then select **Save URLs**.
1. In Gitlab, navigate to the [**Applications**](https://gitlab.com/-/user_settings/applications) page.
1. Select **Add new application**.
1. Enter your app name in **Name**.
1. In **Redirect URI**, paste the **Redirect URI** you saved from the Clerk Dashboard.
1. Select the **Scopes** needed for your app. To allow users to sign up and sign in with GitLab, you must select `read_user` at a minimum.
1. Select **Save application**. You'll be redirected to your app's settings page. Save the **Application ID** and **Secret** somewhere secure. Keep this page open.

### Set the Client ID and Client Secret in your Clerk Dashboard

1. Navigate back to your Clerk Dashboard where the modal should still be open. Paste the **Client ID** and **Client Secret** values that you saved into the respective fields.
1. Navigate back to your Clerk Dashboard where the modal should still be open. Paste the **Application ID** in **Client ID** and **Secret** in **Client Secret**.
1. Select **Add connection**.

> [!NOTE]
Expand Down

0 comments on commit d35062d

Please sign in to comment.