Configuring GitLab Social Connection in Production

This guide outlines the steps to configure GitLab as a social login provider in AuthAction for a production environment.

Step 1: Create a GitLab OAuth Application

1. Go to the GitLab Developer Portal.
2. Click New Application.
3. Fill in the required details:
   • Name: Your application name.
   • Redirect URI: Set the redirect URI to:

     https://<tenant-name>.<region>.authaction.com/oauth2/login/callback
   • Scopes: Choose the scopes based on your requirements, such as read_user for basic user information.
4. Click Save Application.

Step 2: Retrieve Client ID and Client Secret

1. After saving, GitLab will provide you with a Client ID and Client Secret.
2. Copy the Client ID and Client Secret for use in the next steps.

Step 3: Configure GitLab Connection in AuthAction

1. Log in to the AuthAction dashboard.
2. Navigate to Connections → Social Connections.
3. Click Add Connection and select GitLab.
4. Enter the Client ID and Client Secret obtained from GitLab.
5. Click Save.

Step 4: Enable GitLab Connection for Applications

1. In the AuthAction dashboard, navigate to Applications.
2. Select the application for which you want to enable GitLab login.
3. Go to the Connections tab and enable the GitLab connection.

Step 5: Test the Integration

1. Open your application's login page.
2. Click on Sign in with Gitlab.
3. Authenticate using a Gitlab account.
4. Verify that the user is successfully redirected back to your application.

Your application is now configured to allow users to log in using GitLab in production.