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 Gluu Server. This setup guide helps in configuring Single Sign-On (SSO) between the Drupal site and Gluu 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.
Installation Steps
- Using Composer
- Using Drush
- Manual Installation
Configuration Steps
Setup Drupal as OAuth Client:
- After installing the module, navigate to the Configuration -> miniOrange OAuth Client Configuration -> Configure OAuth tab and select Custom OAuth 2.0 Provider from the Select Application dropdown list.
- Copy the Callback/Redirect URL and keep it handy.
- Enter the Display Name as the Gluu.
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.
Setup Gluu as an OAuth Provider:
- Go to Gluu and log into your Gluu account.
- Navigate to OpenID Connect > Client button.
- click the Add Client button.
- You will be shown a form, paste the previously copied Callback URL from Drupal in Redirect Login URIs text field and click on Add button.
- After adding client you will find Client ID and Client Secret for your Gluu application. Copy Client ID & Client Secret and keep it handy. It will require to setup Drupal as OAuth client.
Integrating Drupal with Gluu:
- Go to miniOrange OAuth Client module.
- In Drupal’s Configure OAuth tab paste the copied Client ID and Client Secret from Gluu 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 | openid |
|---|---|
| Authorize EndPoint | https://<gluu-server-domain>/oxauth/restv1/authorize |
| Access Token Endpoint | https://<gluu-server-domain>/oxauth/restv1/token |
| Get User Info Endpoint | https://<gluu-server-domain>/oxauth/restv1/userinfo |
Test Connection between Drupal and Gluu:
- After successfully saving the configurations, please click on the Test Configuration button to test the connection between Drupal and Gluu.
- 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 Gluu. After successfully logging into the Gitlab, you will be provided a list of attributes received from the Gluu.
- 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 Gluu.
- 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 Gluu 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 Gluu 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:
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]
Contact us
[MO_CONTACT_US]
