Time Restriction for Office 365
How can Time Restriction restrict access to Office 365 to our corporate devices?
miniOrange allows you to restrict the use of your application only within a particular time range. Users outside of that timeframe 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.
1. Sync On-Premise Active Directory with Azure Active Directory
NOTE: If you want to use your On-Premise Active Directory as a user store to Single Sign-On into Office 365 then follow the below steps to sync your AD and Azure AD.
- Download the Azure AD Connect
- Run the Azure AD installer on your domain machine and follow the setup.
2. Verify your UPN Domain in Azure Portal
- In the Azure portal navigate to Azure Active Directory >> Custom domain names and click on Add custom domain.
- Enter the full domain name in the right pane that pops up and click on Add domain.
- A new window will open up with TXT/MX records for the domain. You will have to add the resented entry in your domain name registrar.
- Click on verify once you have added the entry
Follow the Step-by-Step Guide given below to configure Time Restriction for Office 365
1. Setup a Custom Branded URL in miniOrange Admin Console
Single Sign-On into Office 365 requires a custom branded URL to be set. Access to miniOrange and connected resources will need to be through the custom branded URL in the format: https://<custom_domain>.xecurify.com/moas
- Login to miniOrange Admin Console.
- Click on Customization in the left menu of the dashboard.
- In Basic Settings, set the Organization Name as the custom_domain name.
- Click Save. Once that is set, the branded login URL would be of the format https://<custom_domain>.xecurify.com/moas/login
2. Configure Office 365 in miniOrange
- Login into miniOrange Admin Console.
- Go to Apps and click on Add Application button.
- In Choose Application Type click on Create App button in SAML/WS-FED application type.
- In the next step, search for Office 365. Click on Office 365 app.
- Make sure the SP Entity ID or Issuer is: urn:federation:MicrosoftOnline
- Make sure the ACS URL is: https://login.microsoftonline.com/login.srf
- Click on Next.
- Configure Name ID based on the User Store you are using:
- Using Active Directory / miniOrange brokering service: Select External IDP Attribute from the dropdown and add objectguid in the text-box that appears.
- Using miniOrange as a User Store: Select Custom Profile Attribute and select a Custom Attribute from the drop-down.
- Set the login policy. You can choose to enable 2FA for login or have users login using a standard username-password.
- Click on Save to configure Office 365.
3. Configure Microsoft Online Services
- Click on Select dropdown and choose Metadata.
- Click on the Download Federate Domain Script button under "INFORMATION REQUIRED TO AUTHENTICATE VIA EXTERNAL IDPS"
- Enter the domain name that you want to federate and click on Download.
Note: You cannot federate your default "onmicrosoft.com" domain. To federate your Office 365 tenant, you must add a custom domain to Office 365.
- After downloading the script, Open PowerShell run the federate_domain script using:
powershell -ExecutionPolicy ByPass -File federate_domain.ps1
- Your domain is now federated. Use the commands below to check your federation settings:
4. 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.
- Now select your Action for behaviour Change and Challenge Type for user from the Action for behaviour Change Section.
Action for behaviour Change Options :
||Allow user to authenticate and use services if Adaptive authentication condition is true.
||Challenge users with one of the three methods mentioned below for verifying user authenticity.
||Deny user authentications and access to services if Adaptive authentication condition is true.
Challenge Type Options :
|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.
- Scroll to the end and click on save.
5. Enable Restriction for Office 365
- 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.
6. 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.
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.
- 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.
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.
||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
||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.