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

1. Configure Atlassian Jira 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 Jira in the list.



• Enter the SP Entity ID or Issuer: https://www.atlassian.com/software/jira/a/your_samlname.
• Enter the ACS URL: https://www.atlassian.com/software/jira/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 Jira 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 Jira 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. Setup SSO in Atlassian Jira Cloud Account

• 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 Adaptive Authentication Policy

• Login to Self Service Console >> Policies >> Adaptive Access Policy section from the left side menu.



• Click on the Create Policy button on the upper right. Add a suitable policy name and click on Create Policy.

3.1 Policy Overview

a. Configure IP Restriction

IP Based Access Restriction allows administrators to control user access based on the source IP address of the login request. Administrators can configure trusted or restricted IP addresses and IP ranges and define the action to be taken when a user's IP address matches the configured criteria. During authentication, the user's IP address is evaluated against the configured policy and access is either Allowed, Denied or Challenged based on the selected configuration.

• Expand the IP Based Access Restriction section by clicking on the dropdown icon to configure IP-based access rules.



• Click Add IP Range to configure IP addresses or IP ranges for the policy.



• Specify the IP Address that you want to whitelist. For the IP Range other than the whitelisted one, you can select the above setting to reflect.
• Choose either Allow or Deny by selecting the corresponding option from the dropdown. If a user tries to login 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 CIDR. You can choose whichever is suitable for you from the dropdown menu.
• You can add multiple IPs or IP ranges by clicking the + Add IP Range button.



• Once the changes are made, click on Next.

b. Configure Device Restriction

Device restriction lets admins control application access using device trust. You can use Agentless Device Restriction (browser-based fingerprinting) or Agent-Based Device Restriction (installed agent with risk scoring) depending on your security requirements.

• Enable the Device Configuration toggle.



• You can configure device restriction using either Agentless or Agent-Based methods:

Agentless Device Restriction

• Number of Device Registrations Allowed: Specifies the maximum number of devices a user can register.
• Enable Mobile Device Restriction: Blocks login attempts from mobile devices.
• Enable Device Auto-Registration: Allows automatic device registration.




Agent-Based Device Restriction

• Prerequisites for enabling Agent-Based Device Restriction:
• All end users must install the Device Agent on their devices before accessing the application.
• Users without the agent are blocked and see: Please install the miniOrange Device Agent on your device and try again.
• The Device Agent is currently supported on Windows devices only.
• Click Download Agent to get the installation file for end users.
• Under Device Registration Method, choose one of the following:
• Self Registration by User: Users can register their own devices up to the defined limit. Provides flexibility with moderate security.



• Number of Device Registrations Allowed: Specifies the maximum number of devices a user can register.
• Enable Mobile Device Restriction: Blocks login attempts from mobile devices.
• Enable Device Auto-Registration: Allows automatic device registration.
• Pre-Approved Trusted Devices Only: Higher security. The admin manually manages trusted device information. Select this option and click Upload Pre-Approved Trusted Devices (CSV) to import devices (you can skip this step if devices are already uploaded).



• Upload a CSV file containing pre-approved users and devices (users must already exist in miniOrange). Download Sample CSV for reference.
• Configure the following options:
• Enable Mobile Device Restriction: Blocks login attempts from mobile devices.
• Enable Device Auto-Registration: Allows automatic device registration.
• Configure Risk Engine for Device Trust Evaluation

  The Risk Engine allows you to evaluate device trustworthiness by analyzing multiple device attributes and calculating a risk score. Based on this score, user access is allowed, challenged or denied during login and device registration.

• Navigate to the Risk Engine section and click Configure.



• Configure Risk Parameters:
• In the Risk Parameters tab, review the list of device attributes grouped by category.
• The Device Identifiers category contains mandatory attributes (such as Installation ID, BIOS UUID, Machine SID, etc.). These attributes are always enabled and cannot be disabled or reprioritized, as they are critical for device fingerprinting.
• For other categories (Hardware, Network, Software, Location), enable the attributes you want to use for device trust evaluation.
• Set a Priority for each enabled attribute:
• High: Strong impact on risk score
• Medium: Moderate impact
• Low: Minimal impact



• Click on Save Changes.
• Configure Risk Score
• In the Risk Score, define the score ranges (0–100) that determine the authentication outcome during user login.
• Lower risk scores indicate trusted devices.
• Higher risk scores indicate potential security risks or anomalies.
• Configure the thresholds as follows:
• Allow: Allow user to authenticate without challenge and registration.
• Challenge: Allow user authentication with a challenge, e.g., when the device limit is exceeded.
• Deny: Deny user authentication, e.g., when the device limit is exceeded, when device attribute is mismatch.

c. Configure Location Restriction

In location restrictions, the admin configures a list of locations where they want to allow or deny end-user access based on the condition set by the admin. When a user tries to log in with Adaptive Access Policy enabled, their location attributes, such as latitude, longitude and country code, are verified against the location list configured by the admin. Based on this, the user will be either allowed, challenged or denied.

• Expand the Location Based Access Restriction section by clicking on the dropdown icon to configure Location Based Access Restriction rules.
• Click on Add Location.



• In the Enter Location input field, enter the Location Name and then select the correct location from the search results using the UP & DOWN navigation keys.
• Add the In and Around Distance for your location in the next input field. This will be the total area in and around the location we have configured using the Latitude and Longitude points.
• In the next select list, select your distance parameter as either KMS (Kilometers) or Miles. For each location you add, you can choose to either allow or deny it by enabling or disabling the switch button next to it.
• You can click on the Add Location to add more than one location.



• Save the changes you made by scrolling down at the bottom of the page.

d. Configure Time Restriction

In time restriction, the admin configures a time zone with start and end times and users are either allowed, denied or challenged based on the condition in the policy. When an end-user tries to log in with Adaptive Access Policy enabled, their time zone-related attributes, such as time zone and current system time, are verified against the list configured by the admin. Based on the configuration, the user is either allowed, denied or challenged.

• Expand the Time Based Access Restriction section by clicking on the dropdown icon to configure Time Based Access Restriction rules.



• Click on Add Time.



• 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, use the dropdown menu to select whether to Allow or Deny it.



• Enter the value in minutes in the input field next to the Login Window Buffer Time (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 6 PM with a time difference value set to 30 minutes, then the policy will consider the time from 5:30 AM to 6:30 PM). If no value is entered in this field, the default value is set which is 0 minutes.
• You can click on the Add Time button to include more than one Time Configuration and then follow the above step.
• Click on Next.

3.2 Action for Behavior Change

• You can configure one of the three possible actions for your Adaptive Access Policy as explained below:




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




Challenge Type Options:




Factors	Description
User Second Factor	The user needs to authenticate using the second factor they have selected or been assigned, such as OTP over SMS PUSH Notification OTP over Email and many more.
KBA	The system will ask the user for 2 of 3 questions they have configured in their Self-Service Console. Only after the correct answers to both questions will the user be allowed to proceed further.
OTP over Alternate Email	User will receive an OTP on the alternate email they have configured through the Self Service Console. Once the user provides the correct OTP, they are allowed to proceed further.

3.3 Email Alerts and Custom Error Message

This section handles the notifications and alerts related to Adaptive Authentication. 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.

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

• Once you have verified all configurations, click Create Policy to save and activate the policy.
• You will see the policy listed once it’s successfully added.

4. Enable Restriction for Atlassian Jira Cloud

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



• Set Group Name and Policy Name as required. 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: Select how IP Restriction should be evaluated when multiple adaptive authentication restrictions are configured.
  • AND: The configured IP Restriction and all other enabled restrictions must be satisfied before access is granted.
  • OR: The configured IP Restriction or at least one other enabled restriction must be satisfied before access is granted.



• Adaptive Authentication Restrictions: Configure additional login restrictions and verification conditions along with the existing configured Restriction to strengthen account security and control user access based on contextual risk factors.

Step 1: Configure SAML app in miniOrange

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



• Under Choose Application, select SAML/WS-FED from the All Apps dropdown.



• In the next step, search for Custom SAML App and click on it .



• In the Basic Settings tab, enter your desired app name and add the SP metadata by clicking the Import SP Metadata button; you can find the metadata in the authentication source tab in CASB.



• Once done, click on Next button.



• In the Attribute Mapping configure attributes according to your choice. click on Save button.

Step 2: Set Up Authentication Source for Atlassian in CASB

• Click here to log in to the miniOrange CASB dashboard.



• Once logged in, you will be redirected to the miniOrange dashboard. Navigate to the "Atlassian" tab and click on the Add App button.



• Select the Add Authentication Source option from the drop-down menu.



• Mention an Authentication name for the authentication source, and click on Generate Metadata.



• After clicking on Generate Metadata, you will get the metadata details, as shown in the image below. Use this data to configure the SAML application in your Identity Provider (IDP).



• If you would like to view the metadata details again, then you can click on the View Metadata button.
• Now, Enter the remaining details like the IDP Entity ID, SAML Login URL, SAML Logout URL, and X509 Certificate which you will find in your Identity Provider metadata. Once done, Choose the Binding Type for SSO Request as required. You will find this information in the IDP metadata. However, if you are not sure, please select the HTTP-Redirect Binding as the default configuration.



• Click the Save & Next button once you have filled out all the details.
• You have now successfully configured SAML Authentication with miniOrange CASB.

Step 3: Configure Basic Settings

• Now, You are redirected to Basic Settings section.
• Fill in the following details to configure the Atlassian Application:

Application Name:	Enter the name of your application
Organization Domain:	Enter the domain of your organization on Shopify. (Ex: example.com)
Attribute Key:	Enter the Group Attribute Key for the SSO app, which you have configured in the IDP under the SAML attributes section.
Name Attribute Key:	Enter the attribute name like fname,Lname etc.
Enter ACS URL:	You can get the ACS URL from the Atlassian Admin dashboard.
Enter Entity URL:	You can get the Entity URL from the Atlassian Admin dashboard.
CASB Type	Select CASB type as Inline or Offline
Enable MDM	If you want to configure MDM on your device, enable it




• Click on Save & Next to save your changes.

Step 4: Configure SAML SSO in Atlassian

• Go to admin.atlassian.com and login with your admin account.



• Navigate to Security > User Security > Identity Providers. Locate the Other provider option and click Choose.



• Enter a name for the Identity Provider Directory and click Add.



• Under the Authenticate users section, click Set up SAML single sign-on.



• Click Next.



• Enter the required SAML details, including Identity Provider Entity ID, Identity Provider SSO URL, and Public x509 certificate, which you will get from Step 2, and then click Next.



• Now, you will get the SP Entity ID and ACS URL. Copy the URLs and paste them into the miniOrange CASB Basic settings, then click Next.



• Select your domain from the drop-down menu and click Next.



• If provisioning is needed, click Set up provisioning. Otherwise, click Stop and Save SAML.



• Navigate to Security > User Security > Authentication Policy and click Edit on your policy.



• Enable the checkbox for Enforce single sign-on.



• Go to the Members tab and click Add members to add members into your directory from the local directory.



• Search for your users in the search bar to add the user or you can add bulk users inside the Bulk entry tab.



• Return to the Settings tab and click Update at the bottom of the page.
• Confirm by clicking Update again in the pop-up.

Step 5: Configure Policies

Let’s see how to configure policies for Atlassian CASB.

• You should be taken to the Manage Policy screen. Enter your policy details, like Policy Name and Policy Description and Select Policies as per your Requirement.



• Follow the below steps to configure restrictions according to your need:

• Once, done with all the configurations click on Save and Next button.

Step 6: Configure Groups

Let’s see how to configure Groups for AtlassianPlus CASB.

• Now, You are redirected to Manage Group screen. Enter the Group Name and Group Description. Select the Atlassian Policy from the drop-down menu.
• Now, we'll proceed to assign permissions for applications to the group.

a) App Restriction: In this, the restrictions will be applied over the application based on the policy that you have configured for the group.

b) No App Restriction: In this, there will be no restrictions on the application for the group.

c) Disable App: By choosing this option, the application becomes inaccessible from anywhere for the entire group.

d) Custom App Restriction: By using this, you can apply an application-specific custom application restriction policy to an application that overpowers the group's restriction policy.




• Now, Click on Save & Next once done.
• After successfully configuring all screens, you will be redirected to the edit screen.

Step 7: Edit Screen

• Basic Settings section You can change any configurations if required in the Authentication.
• Suppose you want to configure different authentication sources. In that case, you can simply click on the Authentication Source in the Navigation Bar, where you will be able to add, view & edit authentication sources.



• In Groups Settings section You can add and configure groups on this screen and view all configured groups.
• Now, Click on Add New Group and you will get a pop-up for adding a new group and you can configure it using the above mentioned steps.



• In the 'Session Management' section, you can see the details of logged-in users' sessions.