SSO Login into Drupal using GitLab as OAuth / OpenID Connect Provider

Overview

Drupal OAuth/OpenID Connect SSO integration enables SSO between the Drupal site and GitLab. This setup guide helps in configuring Single Sign-On (SSO) between the Drupal site and GitLab using the OAuth/OpenID Connect module. When you incorporate the OAuth/OpenID Connect module with the Drupal site, you can log into the Drupal site seamlessly with GitLab credentials. This module is compatible with Drupal 7, Drupal 8, Drupal 9, Drupal 10, and Drupal 11.

Playground Schedule a Meeting

Installation Steps

Configuration Steps

Setup Drupal as OAuth Client:

• After installing the module, navigate to the Configuration -> miniOrange OAuth Client Configuration -> Configure OAuth tab.

• Select Custom OAuth 2.0 Provider from the Select Application dropdown.
• Copy the Callback/Redirect URL and keep it handy.
• Enter the Display Name as the GitLab.


Note: If your provider only supports HTTPS Callback/Redirect URLs and you have an HTTP site, please make sure to enable the 'Enforce HTTPS Callback URL' checkbox at the bottom of the tab.

Create OAuth/OpenID SSO Application in GitLab:

• Go to GitLab and log into your Gitlab account.
• Navigate to the Applications tab and click on Add new application button

• Enter the Name for eg. Drupal.
• Paste the previously copied Callback/Redirect URL from Drupal into the Redirect URI text field.
• Select the Scopes as per your requirements.

• Click on the Save application button. You will be displayed with Application ID and Secret.
• Copy the Application ID and Secret.

Integrating Drupal with Gitlab:

• Go to miniOrange OAuth Client module.
• In Drupal’s Configure OAuth tab paste the copied Client ID and Client Secret from Gitlab in the Client ID and Client Secret text fields.

• Confirm the Scope and Endpoints from the table below and click on the Save Configuration button.

Scope	user repo
Authorize EndPoint	https://github.com/login/oauth/authorize
Access Token Endpoint	https://github.com/login/oauth/access_token
Get User Info Endpoint	https://api.github.com/user

Test Connection between Drupal and Gitlab:

• After successfully saving the configurations, please click on the Test Configuration button to test the connection between Drupal and Gitlab.

• On a Test Configuration popup, if you don't have any active sessions on the same browser, you will be requested to login into the Gitlab. After successfully logging into the Gitlab, you will be provided a list of attributes received from the Gitlab.
• Select the Email Attribute from the dropdown menu in which the user's email ID is obtained and click on the Done button.


Note: Mapping the Email Attribute is mandatory for your login to Gitlab.

• On the Attribute & Role Mapping tab, please select the Username Attribute from the dropdown list and click on the Save Configuration button.

• Now log out and go to your Drupal site’s login page. You will automatically find a Login with Gitlab link there. If you want to add the SSO link to other pages as well, please follow the steps given in the image below:

Congratulations! You have successfully configured Gitlab as OAuth/OpenID Provider and Drupal as an OAuth Client.

Need Assistance?

If you face any issues during the configuration or if you want some additional features, please contact us at drupalsupport@xecurify.com.

Additional Features:

• Attribute Mapping - map user's attributes received from OAuth Provider with Drupal fields
• Role mapping - assign a Drupal Role to users on the basis of their role/attribute on the OAuth provider
• Enable single logout - Logout user from the OAuth Provider (i.e. AWS Cognito, Azure AD B2C, Keycloak, Okta) when they logs out form Drupal
• Restrict anonymous access to the complete site or a particular section of the site
• Add Multiple OAuth Provides
• Explore All the features offered by the OAuth Client

Troubleshooting:

More FAQs ➔

Getting error: 'Username not received. Check your Attribute Mapping configuration.' OR Getting Error: 'Email not received. Check your Attribute Mapping configuration.'

Follow the steps mentioned HERE

I am getting "Client Credentials were not found in the headers or body"
when I try to perform test configuration

Follow the steps mentioned HERE

After I click on the logout in Drupal, it sends me back to the Drupal homepage. However, when I try to login with other user, it doesn't ask me to login but automatically logs me in with same user

The logout functionality you've mentioned here is the default behavior of a module. It's logging you out of Drupal but not from your Application/Provider. To allow the module to logout from your provider/application account (what you are looking for), you need to make the below configurations: [know more]

I purchased the paid Drupal module and replaced it with the free module, but still I am not able to use paid features.

As you have upgraded to one of our paid versions of the Drupal module and replaced the free module with the paid one, you must first activate the paid module. Please refer to the below steps. [Know more]

24/7 Support

The Drupal developers at miniOrange offer quick and active support for your queries. We can assist you from choosing the best solution for your use case.

 Contact us

Case Studies

miniOrange has successfully catered to the use cases of 400+ trusted customers with its highly flexible/customizable Drupal solutions.

 Read more

Other Solutions

Feel free to explore other Drupal solutions that we offer the popular solutions used by our trusted customers include 2FA, User Provisioning, Website Security.

 Know More