• Home
• App Integrations
• Single Sign-On Integrations
• Atlassian Bitbucket Single Sign-On

Atlassian Bitbucket Cloud Single Sign-On(SSO)

Atlassian Bitbucket Cloud Single-Sign On(SSO) or Atlassian Access for enterprises and full control over access of Atlassian Bitbucket Cloud application using a single set of login credentials for secure access using miniOrange SSO solution. Single Sign-on (SSO) into your Atlassian Bitbucket Cloud Account with any of your existing Identity Provider (IDP) or AD credentials for enhanced security.

Atlassian Bitbucket Cloud SSO solution by miniOrange provides secure Single Sign-On access to multiple Atlassian Applications(Jira, Confluence, Bitbucket, Bamboo, Fish eye) as well as other On-Premise and Cloud Apps using a single set of login credentials. With miniorange Identity Provider(IdP) service, you can Single Sign-on(SSO) login to multiple applications using a single Bitbucket cloud Username and Password. Looking at another way, if your users are in any of the third-party Identity Providers (Active Directory, Okta, Auth0) and you want your users to log into Atlassian Bitbucket Cloud/Atlassian Access and other specific applications using existing IDP credentials, you can easily SSO login in a safe and secure manner. Follow the given setup guide to integrate SAML SSO for your Atlassian Bitbucket Cloud.

Follow the Step-by-Step Guide given below for Bitbucket Single Sign-On (SSO)

1. Configure Bitbucket in miniOrange

• Login into miniOrange Admin Console.
• Go to Apps and click on Add Application button.



• In Choose Application, select SAML/WS-FED from the application type dropdown.



• Search for Bitbucket in the list, if you don't find Bitbucket in the list then, search for custom and you can set up your application in Custom SAML App.

• Enter the SP Entity ID or Issuer.
• Enter the ACS URL.
• Enter the Single Logout URL.



• Click Next, now in the Attribute Mapping configure attributes according to your choice.



• Click on the Save button.
• Your application is saved successfully. Now click on the Select button against your newly created application. Go to Metadata.



• On the Metadata page -
  
  1. If you want to use miniOrange as User Store i.e., your user identities will be stored in miniOrange then download the metadata file under the heading 'INFORMATION REQUIRED TO SET MINIORANGE AS IDP'.
  
  2. If you want to authenticate your users via any external Identity Provider like Active Directory, Okta, OneLogin, Google, Apple ID, etc then download the Metadata file under the heading 'INFORMATION REQUIRED TO AUTHENTICATE VIA EXTERNAL IDPS.



• Keep SAML Login URL , SAML Logout URL and click on the Download Certificate button to dowmload certificate which you will require in Step 3.

2. Configure SSO in Bitbucket

• Now login to Atlassian Cloud Admin Console.
• Select your organization and then select Security.



• Select SAML single sign-on and then click Add SAML configuration.



• Enter Identity provider Entity ID, Identity provider SSO URL and Public x509 certificate from Step 1 and click on Save configuration button.

• Now set up the Authentication Policies by clicking on the View Authentication Policies.



• Click on Add Policy.



• Enter the policy name and add the policy.
• Now under Single Sign-On, click on Enable Single Sign-On.



• Then click on the Members tab besides the settings tab and click on Add Members.



• Enter details and click on Add Members. The user must be present in both Atlassian Access and miniOrange. The Single Sign On(SSO) will work only for Added Members.

3. Test SSO Configuration

Test SSO login to your Bitbucket account with miniOrange IdP:

Using SP Initiated Login

• Go to your Bitbucket URL, here you will be either asked to enter the username or click on the SSO link which will redirect you to miniOrange IdP Sign On Page.



• Enter your miniOrange login credential and click on Login. You will be automatically logged in to your Bitbucket account.

Using IDP Initiated Login

• Login to miniOrange IdP using your credentials.



• On the Dashboard, click on Bitbucket application which you have added, to verify SSO configuration.





Not able to configure or test SSO?


Contact us or email us at idpsupport@xecurify.com and we'll help you setting it up in no time.

You can also setup your Atlassian Cloud Application with any IDPs that may support any SSO protocol. To get the Step by Step Atlassian Cloud SSO Configuration, you can view our Cloud SSO Setup Guides .

4. Configure Your User Directory (Optional)

miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Microsoft Entra ID, OpenLDAP, Google, AWS Cognito etc), Identity Providers (like Okta, Shibboleth, Ping, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more. You can configure your existing directory/user store or add users in miniOrange.

5. Adaptive Authentication with Bitbucket

A. Restricting access to Bitbucket with IP Blocking

You can use adaptive authentication with Bitbucket Single Sign-On (SSO) to improve the security and functionality of Single Sign-On. You can allow a IP Address in certain range for SSO or you can deny it based your requirements and you can also challenge the user to verify his authenticity. Adaptive authentication manages the user authentication bases on different factors such as Device ID, Location, Time of Access, IP Address and many more.

You can configure Adaptive Authentication with IP Blocking in following way:

• Login to Self Service Console >> Adaptive Authentication.
• Add a Policy Name for your Adaptive Authentication Policy.



• Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.





Action for behavior Change Options :




Attribute	Description
Allow	Allow user to authenticate and use services if Adaptive authentication condition is true.
Challenge	Challenge users with one of the three methods mentioned below for verifying user authenticity.
Deny	Deny user authentications and access to services if Adaptive authentication condition is true.




Challenge Type Options :




Attribute	Description
User second Factor	The User needs to authenticate using the second factor he has opted or assigned for such as OTP over SMS PUSH Notification OTP over Email And 12 more methods.
KBA (Knowledge-based authentication)	The System will ask user for 2 of 3 questions he has configured in his Self Service Console. Only after right answer to both questions user is allowed to proceed further.
OTP over Alternate Email	User will receive a OTP on the alternate email he has configured threw Self Service Console. Once user provides the correct OTP he is allowed to proceed further.



• Now Enable Enable IP Restriction option from the IP RESTRICTION CONFIGURATION section to configure custom IP range.



• Select the Action you want to perform if the IP address is out of the range. i.e. Allow, Challenge & Deny.
• Specify the IP Address range for which you want above setting to reflect. You can add more than one IP Address ranges by clicking on following button +.
• Scroll to the end and click on save.

B. Adaptive Authentication with Limiting number of devices.

Using Adaptive Authentication you can also restrict the number of devices the end user can access the Services on. You can allow end users to access services on a fixed no. of devices. The end users will be able to access services provided by us on this fixed no. of devices.

You can configure Adaptive Authentication with Device Restriction in following way


• Login to Self Service Console >> Adaptive Authentication.
• Add a Policy Name for your Adaptive Authentication Policy.
• Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.




• Scroll down to Device Configuration section and enable Allow User to Register Device option to allow users to register their devices.
• Enter the Number of Devices which are allowed to register in field next to Number of Device Registrations Allowed
• Choose Action if number of devices exceeded (This will override your setting for Action for behavior Change.)
1. Challenge: The user needs to verify himself using any of the three methods mentioned in table in step 5.1
2. Deny : Deny users access to the system
• Enable option Send email alerts to Users if number of Device registrations exceeded allowed count if you want to alert the user about no of devices exceeding the limit. Save the configuration.

C. Add Adaptive Authentication policy to Bitbucket .

• Login to Self Service Console >> Policies.
• Click on Edit option for predefined app policy.



• Set your application name in the Application and select password as Login Method.
• Enable Adaptive Authentication on Policy page and select the required restriction method as an option.
• From Select Login Policy dropdown select the policy we created in last step and click on save.

D.Notification and Alert Message.

This section handles the notifications and alerts related to Adaptive Authentication.It provides the following options :

• Get email alerts if users login from unknown devices or locations : Admin need to enable this option to enable receiving alerts for different alert options.
  
  
  

Option	Description
Challenge Completed and Device Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge and registers a device.
Challenge Completed but Device Not Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge but do not registers the device.
Challenge Failed	Enabling this option allows you to send an email alert when an end-user fails to complete the challenge.






• Next subsection is Send email alerts which allows us to enable or disable alerts for admin and end-users. To enable alerts for admins, you can enable the “Administrators” switch button.




• In case you want multiple admins accounts to receive alerts then you can enable the option for admin and then enter the admin emails separated by a ‘,’ in the input field next to Administrators email to receive alerts label. To enable alerts for the end-users, you can enable the “End Users” switch button.
• In case you want to customize the deny message that end user receive in case his authentication denied due to adaptive policy, you can do this by entering the message inside “Deny message for Adaptive Authentication” text box.


How to add a trusted Device

1. When End-user log in to the self service console after the policy for device restriction is on, he is provided the option to add the current device as a trusted device.

External References

• Guide For Single Sign On (SSO)
• Bitbucket SAML Single Sign On