OAuth/OpenID Single Sign On (SSO) into Bitbucket using GitLab

Bitbucket OAuth/OpenID app gives the ability to enable OAuth/OpenID Single Sign-On for Bitbucket. Bitbucket is compatible with all OAuth/OpenID Providers. Here we will go through a guide to configure SSO between Bitbucket and GitLab. By the end of this guide, GitLab users should be able to log in and register to Bitbucket.

Step 1: Setup Gitlab as OAuth Provider

  • Login to Gitlab : Sign in to Gitlab and login to your account.
    • Navigate to your profile settings.
    gitlab-1
  • Create app : Select applications in left menu.
  • gitlab-2
    • Provide the required details.
    • Name : This can be anything. Consider something like <Organization>'s GitLab or <Your Name>'s GitLab or something else descriptive.
      Redirect URI : Copy Callback URL from plugin.
      gitlab3

      NOTE: The check-box for “api” needs to be checked, as it’s unchecked by default.

  • Get Client ID & Client Secret : Copy Application Id , Secret and Scope.
  • gitlab4


Step 2: Setup Bitbucket as OAuth Client

  • Use Application Id for Client ID, Secret for Client Secret.
  • Configure Scope as “api”.
  • Click on Test Configuration.
  • gitlab-gif

Step 3: User Profile

    We will be setting up user profile attributes for Bitbucket. If your users are stored in a directory that is Read Only, please check Disable Attribute Mapping in User Profile tab and follow steps given in Matching a User.

    confluence-oauth-openid-sso-user-profile

    a. Finding correct attributes
  • Go to Configure OAuth tab. Scroll down and click on Test Configuration.
  • You will see all the values returned by your Provider to Bitbucket in a table. If you don't see value for First Name, Last Name, Email or Username, make the required settings in your Provider to return this information.
  • Once you see all the values in Test Configuration, keep the window open and go to User Profile tab.
  • b. Setting profile attributes
  • In this tab, fill the values by matching the name of the attribute. For instance, if the Attribute Name in the Test Configuration window is email, enter email against Username.
  • You can configure Email and Username here, otherwise it will create a new user with email address returned in Test Configuration window. If you want existing users to the only login, configure the attribute using which you will match the user in Bitbucket.
  • c. Matching a User
    When the user logs into Bitbucket, one of the user's data/attribute coming in from the Provider is used to search the user in Bitbucket. This is used to detect the user in Bitbucket and log in the user to the same account.
  • Go to User Profile tab.
  • Select Username or Email for Login/Search Bitbucket user account by.
  • Enter the attribute name from Provider which corresponds to Username or Email using Finding Correct Attributes.

Step 4: User Groups

    We will be setting up user group attributes for Bitbucket. If your users are stored in a directory that is Read Only, please check Disable Group Mapping in User Groups tab and skip to Setting default group.

    confluence-oauth-openid-sso-user-groups
    a. Finding Group Attribute
  • Just like we found Attribute Name for User Profile attributes, we find group attribute.
  • Go to Configure OAuth tab. Scroll down and click on Test Configuration.
  • You will see all the values returned by your Provider to Bitbucket in a table. If you don't see value with groups, make the required settings in your Provider to return group names.
  • Once you see all the values in Test Configuration, keep the window open and go to User Groups tab.
  • Enter the Attribute Name of group against Group Attribute.
  • At the bottom of the page, all groups in Bitbucket are shown. You can map groups in Provider which correspond to Bitbucket groups. For example, if you want all users in dev-ops and dev groups in Provider to be added to stash-user, you will need to enter dev-ops;dev against stash-user.

  • b. Setting default group
  • Select the users' Default Group in the tab User Groups. If no group is mapped, users are added by default to this group.

Step 5: Sign In Settings

    The settings in Sign In Settings tab define the user experience for Single Sign On.

  • Set button text for button on login page using Login Button Text.
  • Set redirect URL after login using Relay State. Keep this empty for coming back to the same page user started from.
  • Enable Auto-redirect to Provider if you want to allow users to login only using Provider. Enable backdoor for emergency
  • Backdoor/Emergency URL: Backdoor/Emergency URL gives access to the Application’s default login page. This allows users to log in directly into the application using their local credentials. This will be useful in case the Provider is under maintenance or inaccessible.
  • Domain Restriction : Set domain name which should be allowed for login in Allow Domain. Eg. Allow Domain is miniorange.com then the user with abc@miniorange.com can only able to do login.


  • confluence-oauth-openid-sso-sign-in-settings

If you are looking for anything which you cannot find, please drop us an email on atlassiansupport@xecurify.com