• Home
• App Integrations
• Adaptive Authentication
• Device and IP restriction for Atlassian Bitbucket Cloud

IP, Device, Location and Time Restriction for Atlassian Bitbucket Cloud

---

How can IP Restriction restrict access to Atlassian Bitbucket Cloud to our company offices?

miniOrange allows you to use IP Restriction policy to provide or deny access to the users based on trusted IP Addresses.

• For the IP Restriction to work, the Admin must create a policy specifying permitted IP addresses which allows the access to the application.
• Miniorange supports IP addresses range in three formats i.e. IPv4, IPv4 CIDR and IPv6 CIDR.
• To block the access, Admin must specify an action which needs to be performed when a user tries to login from a non trusted IP address (Such as Deny or Challenge the user with 2FA).
• Once the restriction policy is configured, it can be applied to any application’s login policy to enable IP restriction for that application

How can Device Restriction restrict access to Atlassian Bitbucket Cloud to our corporate devices?

miniOrange allows you to restrict use of your application only within intranet ( office premises ) and blocks user access from outside the network. Additionally you can keep access open for some users from outside the network by creating different groups for them.

• In this restriction method admin allows end-users to add a fixed number of devices as trusted devices for their account.Once a device is registered for a user, that user’s device becomes the trusted device and he will be allowed to login without any restriction.
• When a user initiates the login process for an application for which Device Restriction is enabled, the attributes related to the user's browser session are captured for evaluations.
• Based on these attributes, the miniOrange Adaptive Engine checks and evaluates the decision for that particular user. (i.e Allow, Deny or Challenge with 2FA).
• Based on the decision calculated, the user is redirected to the appropriate action. (i.e Allowed to login if the decision is allow, denied to login if decision is deny or challenged with 2FA if the decision is challenge)

How can Location Restriction restrict access to Atlassian Jira Cloud to our corporate devices?

miniOrange allows you to restrict the use of your application only within a particular range or locatiion. Users outside of that location are not allowed to access the applications.

• Aside from IP and Device, another helpful restriction type is location based restriction. A lot of applications require there to be fine-tuned control over which applications need to be granted access based on the location of the user trying to gain access. Here, miniOrange’s Location-based restriction can easily be set up to scan a user’s access location and enable / disable access accordingly. It can be set up to an accuracy of a few kilometers, and you can have the option to grant access or deny access based on this location data.
• The admin shortlists and configures a list of Geo-locations where they want to allow end-users to either login or deny based on the location set by the admin. When a user tries to login with adaptive authentication enabled, his location attributes such as (Latitude, Longitude, and Country Code) are verified against the Location list configured by the admin, and based on this user will be either allowed, challenged, or denied.

How can Time Restriction restrict access to Atlassian Jira Cloud to our corporate devices?

miniOrange allows you to restrict the use of your application only within a particular time range. Users outside of that location are not allowed to access the applications.

• miniOrange’s Adaptive Engine also offers time-based restriction as one of the methods for Adaptive Authentication. Here, there can be extremely detailed control on the timeframe over which access to your Google Workspace is to be granted or denied for all of your users. miniOrange’s latest Adaptive tech helps you set the days as well as hours in which access is to be controlled, wherein a user can be granted access only within working hours and denied access before as well as after. Time-based restriction is a must have feature when it comes to securing and managing employee working.
• The admin configures a time zone with Start and End Time. Users are either permitted, refused, or challenged based on the timezone and policies defined. When an end-user tries to log in with adaptive authentication enabled, his time zone-related parameters, such as time zone and current system time, are checked against the list defined by the admin, and the user is either permitted, rejected, or challenged, depending on the configuration.

Prerequisite:

• Login into miniOrange Admin Console.
• Click on Customization in the left menu of the dashboard.
• In Basic Settings, set your company domain in Organization Name textfield.
• Click Save. Once that is set, the branded login URL would be of the format https://<company_domain>.xecurify.com/moas/login




Obtain the following information from Atlassian Bitbucket Cloud.

• Domain Verification

  The first step of Atlassian Access starts with the Domain Verification Process to enforce SAML SSO on the managed user accounts. This process verifies that you own a valid domain for managing the user accounts and use the same domain name for the email addresses.

  Once the domain is successfully verified, it lets you host the Jira Software, Jira Service Management (JSM), Bitbucket (wiki), or any Atlassian instance on the Cloud, along with providing pre-generated site URLs. For example, if the verified domain is acma.com, then the Jira Hosting URL will be https://acma.com/jira and user accounts will be user1@acma.com. So you can consider Domain Verification as a crucial step for your instance hosting and anyone who wants to do SAML SSO Configuration on Atlassian Cloud needs to go through the Domain Verification Process. Follow the steps in the document or video for Domain Verification.

• Atlassian Access Subscription

  Atlassian Access is an additional subscription applied across the Atlassian cloud products like Jira Software, Jira Service Management, Jira Work Management, Bitbucket, Bitbucket, etc. So it is needed for Single Sign-On(SSO) or any Cloud Service which comes under Atlassian Access.





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

1. Configure Atlassian Bitbucket Cloud in miniOrange

• Log into miniOrange Admin Console.
• Go to Apps and click on Add Applicaton button.



• In Choose Application Type click on Create App button in SAML/WS-FED application type.



• Search for Bitbucket in the list.



• Enter the SP Entity ID or Issuer: https://www.atlassian.com/software/bitbucket/a/your_samlname.
• Enter the ACS URL: https://www.atlassian.com/software/bitbucket/a/your_samlname.
• Enter the Single Logout URL.



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



• Click on Save.

Get IdP Metadata Details to upload to Atlassian Bitbucket Cloud:

• Go to Apps >> Manage Apps.
• Search for your app and click on the select in action menu against your app.
• Click on Metadata to get metadata details, which will be required later. Click on Link to see the IDP initiated SSO link for Atlassian Bitbucket Cloud.



• Here you will see 2 options, if you are setting up miniOrange as IDP copy the metadetails related to miniOrange, if you required to be authenticated via external IDP's (OKTA, AZURE AD, ADFS, ONELOGIN, GOOGLE APPS) you can get metadata from the 2nd Section as shown below.



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





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. Configure IP Restriction: Restricting access with IP Blocking [This will be released soon]

You can allow an IP Address in a certain range for SSO or you can deny it based on your requirements and you can also challenge the user to verify their authenticity. Adaptive authentication manages the user authentication based on different factors such as Device ID, Location, Time of Access, IP Address and many more, thus improving the security and functionality of Single Sign-On.

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

• Navigate to Policies >> Adaptive Access Policy from the left navigation menu.
• Click on Create Policy.



• Enter a Policy Name for your Adaptive Authentication Policy in the required field and click on Create Policy.




1. Configure Policy Condition:

• Click on the Down Arrow button in the IP Based Access Restriction section.



• Click on the Add IP Range button to add a new IP address or IP range to the policy.



• Enter the IP address or IP range that should be evaluated by the policy. Select whether authentication attempts from the specified range should be Allowed or Denied.
• If a user tries to log in with the whitelisted IP address, they will always be allowed access.
• We support IP address range in three formats i.e., IPv4, IPv4 CIDR and IPv6. You can choose whichever is suitable for you from the dropdown menu.



• You can add multiple IP address and IP ranges by clicking on the Add IP Range.



• Click on Next.

2. Configure Action for Behaviour Change:

• Select the action that should be applied when a user's IP address matches or does not match the configured policy conditions.




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 Types:




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 many more.
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.



• Scroll to the end and click on save.

3. Email Alerts and Custom Error Message

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

• Send email alerts: Configure the recipients who should receive email notifications when adaptive authentication events occur. Alerts can be sent to administrators, end users or both, depending on your monitoring and security requirements.



• Send email alerts to administrators: Enable this option to notify administrators when configured adaptive authentication events are triggered. You can optionally specify an email address under Administrator's e-mail address to receive alerts to receive alerts; otherwise, alerts are sent to the default administrator account.
• Send email alerts to end users: Enable this option to notify end users when adaptive authentication events affect their login attempts or device registrations.
• Number of Device Registrations Exceeded Allowed Count: When enabled, end users receive an email notification if they attempt to register more devices than the maximum number allowed by the configured device restriction policy. (Available only for end-user notifications.)



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



Option	Description
Users login from unknown IP addresses, devices or locations	Enabling this option allows you to login from unknown IP addresses or devices and even locations.
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.





• In case you want multiple admin 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 Administrator's email to receive alerts label. To enable alerts for the end users, you can enable the End User checkbox.
• In case you want to customize the deny message that the end user receives in case his authentication is denied due to adaptive policy, you can do this by entering the message inside Deny Message text box.



• Click on Next to continue.

4. Review

Review the configured policy conditions, behavior change actions, email alert settings and custom error messages before creating the adaptive authentication policy. This step provides a consolidated view of all configured settings, allowing you to verify the policy configuration and make any necessary changes before saving.




• Click on Create Policy.

Enable Restriction for Atlassian Bitbucket Cloud

• Login to Self Service Console >> Policies >> App Login Policy.
• Click on the Edit icon for the predefined app policy.



• Set your policy in the Policy Name and select Password as First Factor.



• Enable Adaptive Authentication on Edit Login Policy page and select the required restriction method as an option.
• From Select Login Policy dropdown select the policy we created in last step.
• Apply Restrictions Using: Configure how multiple adaptive authentication restrictions should be evaluated during user login.
  • AND: All enabled restrictions must be successfully satisfied for the login attempt to be allowed.
  • OR: At least one enabled restriction must be successfully satisfied for the login attempt to be allowed.



• Adaptive Authentication Restrictions: Configure additional login restrictions and verification conditions to strengthen account security and control user access based on contextual risk factors.
  • IP Restriction: Restrict login access to specific IP addresses or IP ranges for enhanced security.
  • Device Restriction: Allow login access only from trusted or pre-authorized devices.
  • Location Restriction: Control user login access based on geographic location.
  • Time Restriction: Restrict user login access to specific days or time periods.
  • Force MFA On Each Login Attempt: Require users to complete MFA verification during every login attempt regardless of device or session state.







4. Configure Device Restriction: Restricting access by Limiting the 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. When Device for a policy is enabled, the Enduser's device will be matched to previously registered device for that user. The end users will be able to access services provided by us on this fixed no. of devices of that particular user.

You can configure Adaptive Authentication with Device Restriction in following way:

• Go to Adaptive Authentication from the left navigation bar.
• Click on Add Policy tab.



• Add a Policy Name for your Adaptive Authentication Policy.



• Scroll down to Device Configuration section and click on Edit.
• Enter the Number of Devices which are allowed to register in field Number of Device Registrations Allowed.



• You can enable or disable the Mobile Device Restriction to ensure if the login attempts from mobile devices will be accepted or declined.
• Similarly, you can enable or disable MAC Address Based Restriction.



• Now, scroll down to the Action For Behaviour Change section and click on Edit. Select the action you want to perform if the IP address is out of the range. i.e. Allow, Challenge or Deny.



• Scroll to the end and click on save.



5. Configure Location Restriction: Restricting access by Limiting the number of locations

In this restriction method, admin configures a list of locations where we want to allow end-users to either login or deny based on the condition set by the admin. When a user tries to login with adaptive authentication enabled, his Location Attributes such as (Latitude, Longitude and Country Code) are verified against the Location list configured by the admin. And based on this user will be either allowed, challenged or denied.

You can configure Adaptive Authentication with Location Restriction in following way:


• Go to Adaptive Authentication from the left navigation bar.
• Click on Add Policy tab.



• Add a Policy Name for your Adaptive Authentication Policy.



• Scroll down to Location Configuration section and click on Edit.



• Here, you can Enable Location Registration if User Completes Challenge.
• Under Configured Locations, click on Add Location.



• In the Enter Location input field, enter the Location Name and then select the correct location from the search results dropdown. Next, select your distance parameter as either KMS(KiloMeters) or Miles under Allowed Radius. For each Location you add, you can choose to either whitelist/allow or blacklist/deny it by selecting the suitable option.
• You can click on the Add Location to add more than one location and then follow steps as mentioned above.



• Now, scroll down to the Action For Behaviour Change section and click on Edit. Select the action you want to perform if the IP address is out of the range. i.e. Allow, Challenge or Deny.



• Scroll to the end and click on save.



6. Configure Time Restriction: Restricting access by Limiting the Time Zones

In this restriction method admin configures a time zone with Start and End Time's for that time zone and users are either allowed, denied or challenged based on the condition in the policy. When an end-user tries to login with the adaptive authentication enabled, his time zone related attributes such as Time-Zone and Current System Time are verified against the list configured by the admin and based on the configuration the user is either allowed, denied or challenged.

You can configure Adaptive Authentication with Time Restriction in the following way:


• Go to Adaptive Authentication from the left navigation bar.
• Click on Add Policy tab.



• Add a Policy Name for your Adaptive Authentication Policy.



• Scroll down to Time Configuration section and click on Edit.



• Here, you can Enable Time Registration if User Completes Challenge.
• Enter the a value in minutes in the input field of Time Difference allowed for Fraud Prevention check (In Minutes). This value allows you to specify some relaxation before your start time and after your end time. (so if the start time is 6 AM and the end time is 6PM with a time difference value set to 30 minutes, then the policy will consider time from 5:30AM to 6:30 PM). If no value is entered in this field, the default value is set which is 15 minutes.



• Under Configured Time, click on Add Time. Select a day/days from the Select Days dropdown. From the Select Timezone list, select the timezone. From the Start Time and End Time lists select the appropriate values. For each Time configuration you add, you can choose to either whitelist/allow or blacklist/deny it by selecting the suitable the option.
• You can click on the Add time button to add more than one Time Configurations and then follow steps as mentioned above.



• Now, scroll down to the Action For Behaviour Change section and click on Edit. Select the action you want to perform if the IP address is out of the range. i.e. Allow, Challenge or Deny.



• Scroll to the end and click on save.



7. Enable Restriction for Bitbucket Cloud

• Go to Policies >> App Login Policy from the left navigation bar.
• Click on Edit option against your selected app.



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




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.




8. 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.



• Setup miniOrange as IDP
• Setup AD as User Directory
• Setup External IDP


• To add your users in miniOrange there are 2 ways:
• Create User in miniOrange
• Bulk Upload Users
1. Create User in miniOrange
• Click on Users >> User List >> Add User.



• Here, fill the user details without the password and then click on the Create User button.



• After successful user creation a notification message "An end user is added successfully" will be displayed at the top of the dashboard.



• Click on Onboarding Status tab. Check the email, with the registered e-mail id and select action Send Activation Mail with Password Reset Link from Select Action dropdown list and then click on Apply button.



• Now, Open your email id. Open the mail you get from miniOrange and then click on the link to set your account password.
• On the next screen, enter the password and confirm password and then click on the Single Sign-On (SSO) reset password button.



• Now, you can log in into miniOrange account by entering your credentials.
2. Bulk Upload Users in miniOrange via Uploading CSV File.
• Navigate to Users >> User List. Click on Add User button.



• In Bulk User Registration Download sample csv format from our console and edit this csv file according to the instructions.



• To bulk upload users, choose the file make sure it is in comma separated .csv file format then click on Upload.



• After uploading the csv file successfully, you will see a success message with a link.
• Click on that link you will see list of users to send activation mail. Select users to send activation mail and click on Send Activation Mail. An activation mail will be sent to the selected users.
• Click on Identity Providers >> Add Identity Provider in the left menu of the dashboard



• In Choose Identity Provider, select AD/LDAP Directories from the dropdown.



• Then search for AD/LDAP and click it.



• STORE LDAP CONFIGURATION IN MINIORANGE: Choose this option if you want to keep your configuration in miniOrange. If the active directory is behind a firewall, you will need to open the firewall to allow incoming requests to your AD.
• STORE LDAP CONFIGURATION ON PREMISE: Choose this option if you want to keep your configuration in your premise and only allow access to AD inside premises. You will have to download and install miniOrange gateway on your premise.




• Enter AD/LDAP Display Name and Identifier name.
• Select Directory Type as Active Directory.
• Enter the LDAP Server URL or IP Address against the LDAP Server URL field.
• Click on the Test Connection button to verify if you have made a successful connection with your LDAP server.



• In Active Directory, go to the properties of user containers/OU's and search for the Distinguished Name attribute. The bind account should have minimum required read privileges in Active Directory to allow directory lookups. If the use case involves provisioning (such as creating, updating, or deleting users or groups), the account must also be granted appropriate write permissions.



• Enter the valid Bind account Password.
• Click on the Test Bind Account Credentials button to verify your LDAP Bind credentials for LDAP connection.



• Search Base is the location in the directory where the search for a user begins. You will get this from the same place you got your Distinguished name.



• Select a suitable Search filter from the drop-down menu. If you use User in Single Group Filter or User in Multiple Group Filter, replace the <group-dn> in the search filter with the distinguished name of the group in which your users are present. To use custom Search Filter select "Write your Custom Filter" option and customize it accordingly.



• Click on the Next button, or go to the Login Options tab.
• You can also configure following options while setting up AD. Enable Activate LDAP in order to authenticate users from AD/LDAP. Click on the Next button to add user store.




Here's the list of the attributes and what it does when we enable it. You can enable/disable accordingly.

Attribute	Description
Activate LDAP	All user authentications will be done with LDAP credentials if you Activate it
Fallback Authentication	If LDAP credentials fail then user will be authenticated through miniOrange
Enable administrator login	On enabling this, your miniOrange Administrator login authenticates using your LDAP server
Show IdP to users	If you enable this option, this IdP will be visible to users
Sync users in miniOrange	Users will be created in miniOrange after authentication with LDAP



• Click on the Next button, or go to the Attributes tab.
Attributes Mapping from AD
• By default userName, firstName, lastName, email are configured. Scroll down and click on Save button. To fetch additional attributes from Active Directory, enable Send Configured Attributes. On the left side, enter the name that you wish to release to the applications. On the right side, enter the attribute name from Active Directory. E.g., if you wish to fetch company attribute from Active Directory, and send it as organization to configured applications, enter the following:

  Attribute Name sent to SP = organization
  Attribute Name from IDP = company






• Click on the Next button, or go to the Provisioning tab.
User Import and Provisioning from AD
• If you want to set up provisioning, click here for detailed information. We will skip this step for now.



Import Password Policy from AD
• If you want to import your Active Directory password policy into miniOrange, click here for detailed information. We will skip this step for now.



Test Connections
• You will see a list of directories under Identity Providers. From the dropdown, select AD/LDAP Directories, search for your configured directory, click the three dots next to it, and select Test Connection.



• A pop-up appears prompting you to enter a username and password to verify your LDAP configuration.



• On Successful connection with LDAP Server, a success message is shown.



Test Attribute Mapping
• You will see a list of directories under Identity Providers. From the dropdown, select AD/LDAP Directories, search for your configured directory, click the three dots next to it, and select Test Attribute Mapping.



• A pop‑up appears to enter a username and click Test.



• The Test Attribute Mapping Result will be displayed.



Set up AD as External Directory configuration is complete.


Note: Refer our guide to setup LDAP on windows server.
miniOrange integrates with various external user sources such as directories, identity providers, and etc.
• Okta
• ADFS
• Ping
• AWS Cognito
• Many more
Not able to find your IdP or Need help setting it up?


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





External References

• miniOrange Adaptive Authentication
• Atlassian Bitbucket Cloud Single Sign-on (SSO)
• What is Atlassian Bitbucket Cloud?