SAML Single Sign On (SSO) Into Bitbucket Using RSA SecurID

Bitbucket SAML app gives the ability to enable SAML Single Sign On for Bitbucket Software. Bitbucket Software is compatible with all SAML Identity Providers. Here we will go through a guide to configure SSO between Bitbucket and RSA SecurID. By the end of this guide, RSA SecurID users should be able to login and register to Bitbucket Software.

Step 1:Setup RSA SecurID as Identity Provider

All the information required to configure RSA i.e. plugin’s metadata is given in the Service Provider Info tab of the miniOrange plugin.


  • Login to the RSA Secure ID as Super Admin.
  • In the Administration Console, click Application → Application Catalog.
  • Click Create From Template button on the top right corner.

    RSA SecurID sso-1
  • Next to the SAML Direct, click select in the Choose Connector Template page. The Add Connector wizard appears.

    RSA SecurID sso-2
  • Fill the required information in the Basic Information page on the Add Connector wizard.

    • Name:- Name of the application for eg. miniOrange Plugin.
    • Description (Optional):- Description for your application.
    • Disabled [a checkbox] (optional): Select this only if you want to make this application unavailable to users. When disabled, the application appears in My Application but does not appear in the RSA application portal.
    • Click Next Step button.

      RSA SecurID sso-3
  • Fill the required information in the Connection Profile page.
  •   Connection Profile

    • Upload the miniOrange plugin’s metadata file and click on the Import Metadata button. You can download it from the Service Provider info tab of the plugin.
    • Verify the configured URLs and clicks on the Save button on the top right corner of the pop-up window.

      RSA SecurID sso-4

      Initiate SAML Workflow

    • Select SP-Initiated, if you want the SSO should be invoked from Application or select IDP-initiated, if you want the user should log in into RSA first and then access Application from his RSA Dashboard.
    • Configure base URL of your Application or you can leave it blank if IDP-initiated is selected.
    • Select Binding type: POST and Signed Checked.

      RSA SecurID sso-5

      SAML Identity Provider(Issuer)

    • Upload the public and private key which will be used to signed SAML Response or you can generate new key pair by clicking on the Generate Cert Bundle button.
    • (Optional) Enable checkbox for Include Certificate in Outgoing Assertion.

      RSA SecurID sso-6

      Service Provider

    • Assertion Consumer Service URL and Audience URL should be preconfigured if you have uploaded plugin’s metadata in the Connection Profile section. If not, you can find the required URLs from Service Provider Info tab of the miniOrange SAML plugin and update the URL here.

      RSA SecurID sso-7>
</ul>
</div>
<div style=

        User Identity

      • Configure NameID information that identifies the user on whose behalf the SAML Assertion is generated.

        RSA SecurID sso-8

      Advanced Configuration: Attribute Extention

    • Configure additional user information to be sent to the Application in the SAML Response, for example, username, email, display name, groups etc.

      RSA SecurID sso-9

      Advanced Configuration: Uncommon Formatting SAML Response

    • Sign outgoing Assertion:- Assertion within Response.
    • Encrypt Assertion (Optional): If checked, you need to load miniOrange plugin’s public certificate and you can download it from the Service Provider Info tab of the plugin.
    • Unchecked Send encoded URL in Assertion.
    • Checked include issuer NameID format and select NameID Format as Unspecified.
    • Save the configuration and move to the next page i.e. User Access page.

      RSA SecurID sso-10
  • Define application access in the User Access page.
  • Configure application display settings for RSA end users like app icon etc and save the settings
  • Now, In the Administration Console, click Application My Application.
  • Find the app that you have configured and click on Edit Export Metadata. Keep the metadata handy, it will require to configure miniOrange plugin.

    RSA SecurID sso-11
  • Click on Publish Changes in the top left corner of the RSA Admin Console to publish this configuration and immediately activate it.

    RSA SecurID sso-12

Step 2: Setup Bitbucket as Service Provider

Now we will go through the steps to setup Bitbucket as a Service Provider using miniOrange add-on:

Configuring Single IDP

With the information you have been given by your IDP team, you can configure IDP settings in 3 ways:

A. By Metadata URL

  • Click on Import from Metadata in Configure IDP tab
  • Select IDP: Import From Metadata URL
  • Enter IDP metadata URL: Enter your metadata URL
  • If your IDP changes certificates at intervals, you can select Refresh metadata periodically. Select 5 minutes for the best results.
  • Click Import

bitbucket sso-8

B. By uploading Metadata XML file

  • Click on Import from Metadata in Configure IDP tab
  • Select IDP: Import from Metadata File
  • Upload metadata file
  • Click Import

bitbucket sso-9

C. Manual Configuration

Go to Configure IDP tab and enter the following details

  • IDP Entity ID
  • Single Sign On URL
  • Single Logout URL
  • X.509 Certificate
bitbucket sso-10
Configure New IDP

If you already have one IDP & you are looking to add Second IDP then you can do it by performing the following steps.

  • Navigate to Configure IDP tab.
  • Click on Add new IDP.
  • It will present a blank form & you can configure new IDP using steps from Single IdP Setup.


Configure multiple IDPs

If you have configured more than two IDPs then it will show you the list of IDP that you have configured with Bitbucket.

Click on Add new IdP button for adding new IDP on Bitbucket. The steps for adding new IDP will remain the same.


An operation that you can perform with List of IdPs page.

  • Add / delete Identity Provider.
  • Test Connection between Bitbucket & IdP by click on Test button for respective IDP.
  • Edit the IdP configuration by clicking on the Edit button.
  • You can allow an only specific set of users to access Bitbucket by using Domain Mapping.

Single Sign-On with Multiple Identity Provider(IDP)

Select your IdP from the list. It will redirect you to selected IdP login page.


Configure Domain Mapping

You can enable domain mapping using Use Domain Mapping option.
Once enable it, you need add domain name against each IDP.
After enabling Domain Mapping it allows SSO only for those users whose domain matches with the specified one.



Single Sign-On using Domain mapping

Enter the user email address. It will check your domain name with the configured domain if it matches then it will redirect you to the respective Identity Provider Login page.


This is how the login screen would appear after enabling domain mapping.

Step 3: Setting up Bitbucket user profile attributes

    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 user Profile Mapping in User Profile tab and follow steps given in Matching a User.

    bitbucket sso-11

    a. Finding correct attributes
  • Go to Configure IDP tab. Scroll down and click on Test Configuration.
  • You will see all the values returned by your IDP 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 IDP 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 NameID, enter NameID against Username
  • Setting up both Username and Email is required if you want to let users register. 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 IDP 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 IDP which corresponds to Username or Email using Finding Correct Attributes

Step 4: Assigning groups to users

    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.

    bitbucket sso-12
    a. Finding Group Attribute
  • Just like we found Attribute Name for User Profile attributes, we find group attribute.
  • Go to Configure IDP tab. Scroll down and click on Test Configuration.
  • You will see all the values returned by your IDP to Bitbucket in a table. If you don't see value with groups, make the required settings in your IDP 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 IDP which correspond to Bitbucket groups. For example, if you want all users in dev-ops and dev groups in IDP to be added to crucible-users, you will need to enter dev-ops;dev against crucible-users
  • If you want user mapping to work for only limited groups in Bitbucket, check the option Update User Groups

  • b. Setting default group
  • Select the users Default Group to assign SSO users. Recommended to set up the groups needed to access the application.
  • You can enable default groups for all users or new users using the option.Select Noneif you don't want to assign any default group to SSO users.Using the option Enable Default Groups for.

Step 5: SSO Settings

    The settings in SSO Settings tab define the user experience for Single Sign On.
    a. Sign In Settings
  • Set Enable SSO for Bitbucket Server to allow SSO for Bitbucket users.
  • 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 IDP if you want to allow users to login only using IDP. Enable backdoor for emergency
  • bitbucket sso-13
    b. Custom Login Template
  • Design your own login template that will be used to intitate SSO.

  • c. Sign Out Settings
  • Set Logout URL or Logout Template to redirect users after logout action.
  • bitbucket sso-14
    d. SSO Error Settings
  • Set error template to redirect users to a custom error page instead of login page. Use this if you have Auto-redirect to IDP enabled.
  • bitbucket sso-15
    e.Advanced Settings
  • Allow Users to Change Password: Disable if you don't want user to chnage their local Bitbucket credential
  • Remember Me-cookie: If enabled, user stays logged in until user explicitly logs out.
  • You can extend Bitbucket default session timeout using these steps. By default it is set to 30 mins.
  • Validate IDP's SAML Response: Configure time difference(in minute) here In case Bitbucket server time is not in sync with your IDP's time.

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