IP, Device, Location and Time Restriction for Atlassian Jira Cloud
How can IP Restriction restrict access to Atlassian Jira 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 Jira 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.
Connect with External Source of Users
miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Azure AD, OpenLDAP, Google, AWS Cognito etc), Identity Providers (like Shibboleth, Ping, Okta, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more.
Prerequisite:
Follow the Step-by-Step Guide given below for Atlassian Jira Cloud Single Sign-On (SSO)
1. Configure Atlassian Jira Cloud in miniOrange
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 IP Restriction: Restricting access with IP Blocking
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. 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
- Go to Adaptive Authentication from left navigation bar.
- Click on Add Policy tab.
- Add a Policy Name for your Adaptive Authentication Policy.
- 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 Behaviour Change.)
- Challenge: The user needs to verify himself using any of the three methods mentioned in table in step 2.1
- Deny : Deny users access to the system
- Select your Action for behaviour Change and Challenge Type for user from the Action for behaviour Change Section.
- 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.
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
- On the Add Policy tab navigate to LOCATION CONFIGURATION section and enable the Enable Location Based Restriction option.
- 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 + button to add more than one location and then follow steps 2-4 as mentioned above.
- Scroll down to the bottom of the page 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:
- On the Add Policy tab navigate to TIME OF ACCESS CONFIGURATION section and enable the Enable Time Based Restriction option.
- 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 allow or deny it by enabling or disabling the switch button next to it.
- Enter the a value in minutes in the input field next to Time Difference allowed for Fraud Prevention check. 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.
- You can click on the + button to add more than one Time Configurations and then follow step 2 as mentioned above.
7. Enable Restriction for Jira 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
- 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, Azure AD, 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.
- Click on External Directories >> Add Directory in the left menu of the dashboard.
- Select Directory type as AD/LDAP.
- STORE LDAP CONFIGURATION IN MINIORANGE: Choose this option if you want to keep your configuration in miniOrange. If 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 in your premise.
- Enter LDAP Display Name and LDAP Identifier name.
- Select Directory Type as Active Directory.
- Enter the LDAP Server URL or IP Address against LDAP Server URL field.
- Click on 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 Distinguished Name attribute.
- Enter the valid Bind account Password.
- Click on 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. To use custom Search Filter select "Write your Custom Filter" option and customize it accordingly.
- You can also configure following options while setting up AD. Enable Activate LDAP in order to authenticate users from AD/LDAP. Click on the Save 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 |
| Sync users in miniOrange |
Users will be created in miniOrange after authentication with LDAP |
| Fallback Authentication |
If LDAP credentials fail then user will be authenticated through miniOrange |
| Allow users to change password |
This allows your users to change their password. It updates the new credentials in your LDAP server |
| 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 |
| Send Configured Attributes |
If you enable this option, then only the attributes configured below will be sent in attributes at the time of login |
- Click on Save. After this, it will show you the list of User stores. Click on Test Connection to check whether you have enter valid details. For that, it will ask for username and password.
- On Successful connection with LDAP Server, a success message is shown.
- Click on Test Attribute Mapping.
- Enter a valid Username. Then, click on Test. Mapped Attributes corresponding to the user are fetched.
- After successful Attribute Mapping Configuration, go back to the ldap configuration and enable Activate LDAP in order to authenticate users from AD/LDAP.
Refer our guide to setup LDAPS on windows server.
User Import and Provisioning from AD
- Go to Settings >> Product Settings in the Customer Admin Account.
- Enable the "Enable User Auto Registration" option and click Save.
- (Optional) To send a welcome email to all the end users that will be imported, enable the "Enable sending Welcome Emails after user registration" option and click Save.
- From the Left-Side menu of the dashboard select Provisioning.
- In Setup Provisioning tab select Active Directory in the Select Application Drop Down.
- Toggle the Import Users tab, click on Save button.
- On the same section, switch to Import Users section.
- Select Active Directory from the dropdown and click on the Import Users tab, to import all the users from Active Directory to miniOrange.
- You can view all the Users you have imports by selecting Users >> User List from Left Panel.
- All the imported users will be auto registered.
- These groups will be helpful in adding multiple 2FA policies on the applications.
miniOrange integrates with various external user sources such as directories, identity providers, and etc.
External References
