Office 365

miniOrange provides secure access to Office 365 for enterprises and full control over access to the applications, Single Sign On (SSO) into your Office 365 Account with one set of login credentials, eliminating user-managed passwords and the risk of phishing. The solution leverages the existing on-premise Active Directory infrastructure and provides for a seamless integration without the need to manage multiple on-premise and cloud identities.

miniOrange supports both IdP (Identity Provider) and SP (Service Provider) initiated Single Sign-on (SSO)

• IdP Initiated Single Sign On (SSO)

  In IdP Initiated Login, SAML request is initiated from miniOrange IdP.

• Enduser first authenticates through miniOrange Idp by login into miniOrange Self Service Console.
• The Enduser will be redirected to their Office 365 account by clicking the Office 365 icon on the Enduser Dashboard - there is no need to log in again.

• SP Initiated Single Sign On (SSO)

  In SP Initiated Login, SAML request is initiated by Office 365.

• An Enduser tries to access their Office 365 domain.
• They will be redirected to miniOrange Self Service Console.
• Here they can enter the miniOrange login credentials and login to their Office 365 Account.

Step 1: Prepare your Active Directory Domain

• Office 365 SSO requires an Internet-resolvable domain name to use as the suffix in each user’s username. Don’t worry, though, if your Active Directory domain name doesn’t meet this requirement. Most of them don’t. You can make things work by giving users an alternate User Principal Name (UPN) that matches any public domain name you own.
  
• Let’s assume your public domain name is mydomain.com, but your inside-the-firewall Active Directory domain is mydomain.local. You can’t resolve mydomain.local via Internet servers, therefore you won’t be able to with Office 365 DNS servers. That said, you can use federation to set each user’s UPN to a publicly resolvable domain name and let them log in as username@mydomain.com.
  
• While each user’s UPN might look like an e-mail address, it has nothing to do with SMTP or Session Initiation Protocol. This change merely maps your users’ Active Directory accounts with an external address that Office 365 can understand.
  
• Launch Active Directory Domains and Trusts and view the Properties of its top-level node. In the box titled Alternative UPN suffixes, enter your publicly resolvable domain name and click Add. Then launch Active Directory Users and Computers and view the Properties of a user account. Under its Account tab, you can now set the User login name to that publicly resolvable domain name. Do this for each Office 365-enabled user. They’ll be using this as their Office 365 username in a minute.
  
  

Step 2: 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##.miniorange.com/moas.

• Login to miniOrange Admin Console.
• Navigate to Customization->Branding Customization
• Under Basic Settings, set the Organization Name as the custom domain name. Once that is set, the branded login URL would be of the format https://##CUSTOM DOMAIN##.miniorange.com/moas.



• Click on Save.

Step 3: Choose Your User Directory

3.1: Setup AD as User Directory

1. Log in to miniOrange dashboard from the Admin Console.
2. From the Side Menu, Click on User Stores >> Add User Store
   
   

   
   
   

3. Select User Store type as AD/LDAP.





1. 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.
2. 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.
   
   



4. Enter LDAP Display Name and LDAP Identifier of your choice. Select Directory Type as Active Directory.
5. Enter the LDAP Server URL or IP Address against LDAP Server URL field.
6. Go to AD FS-> Domain-> respective Users -> Properties-> Attribute Editor. Now copy the value of distinguishedName and paste it against Bind Account DN.



7. Enter the valid password for the user from above step.
8. Search Base is the location in the directory where the search for a user begins.



9. If you want to add extra conditions on user search you can add it in Search Filter. Select a suitable Search Filter from the Drop-Down. To use custom Search Filter select "Custom Search Filter" option and provide the search filter in the input field that shows up.



10. You can also configure following options while setting up AD.




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
Backup 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



11. Click on Save. After this, it will show you the list of User stores. Click on Test Configuration to check whether you have enter valid details. For that, it will ask for username and password.



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



13. Click on Test Attribute Mapping.



14. Enter a valid Username. Then, click on Test. Mapped Attributes corresponding to the user are fetched.



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

3.2: Setup miniOrange as a User Store

1. Log in to miniOrange dashboard from the Admin Console.
2. There are 3 ways to setup miniOrange as an Identity Source

3.2.1 Create User in miniOrange

3.2.2 Bulk Upload Users

3.2.3 Self User Registration




3.2.1 Create User in miniOrange

• Click on Users >> Add User.



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



• Click on On Boarding 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.



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



3.2.3 Self User Registration

• miniOrange self user registration allows end users to register themselves using customized registration form. miniOrange admin users can customize the registration form by adding more custom fields accodring to their choice. Learn More

Step 4: Add Your UPN Domain to Office 365

• If the publicly resolvable domain name you choose isn’t already linked to Office 365, do so via the Microsoft Online Services Portal. Click Domains in the Admin console and then select Add a domain. The wizard will prompt you for the domain name, and then give you one of two options for authenticating ownership. You’ll need to add either a TXT or MX record to the publicly accessible DNS server hosting the domain.
  
• It can take anywhere from 15 minutes to 72 hours for the update to fully propagate, so it might take a while before you can complete the validation process. Validation affirms to Office 365 that you own the domain name your clients will later use to authenticate. You don’t need to have any servers within this domain for federation to function. All you need to complete this step is the domain itself that you can resolve from the Internet.
  
  

Step 5: Follow the Step-by-Step Guide given below for Office 365 Single Sign On (SSO)

Step 5.1 Configure Single Sign On (SSO) Settings

• Login to miniOrange Admin Console.
• Go to Apps >> Manage Apps. Click on Add Application button.



• Click on SAML tab and 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.
• Add an attribute with attribute name as IDPEmail and select attribute value as E-mail Address.
• Set the authentication policy. You can choose to enable 2FA for login or have users login using a standard username-password.
• Click on Save to configure Office365.



• Click on Metadata link to see the Identity Provider information required to configure Office 365. Note down the following information.
  • IdP Entity ID/Issuer
  • Logout URL
  • Login URL
  • X.509 Certificate

Step 5.2: Configure Microsoft Online Services

• Open Powershell in Administrator Mode. The Microsoft Online Services module needs to be installed for the below commands to run.
• Install-Module -Name AzureAD
• If prompted about installing a module from an untrusted repository, type Y and press ENTER.
• Install the 64-bit version of the Microsoft Online Services Sign-in Assistant. Download it from here.
• Run the Following command in Powershell to install MSOnline Module : Install-Module MSOnline
• If prompted to install the NuGet provider, type Y and press ENTER.
• If prompted to install the module from PSGallery, type Y and press ENTER.
• Execute the following Powershell commands:
  • $cred = Get-Credential. Enter Office 365 Administrator credentials.
  • Connect-MsolService -Credential $cred.
  • Replace the following information with the one noted in above step:
    • Replace ##DOMAIN NAME## by your Active Directory Domain Name. Ensure that the domain is not the default domain name as the default one cannot be set as the federated domain
    • Replace ##IDP ENTITY ID## with the IdP Entity ID/Issuer Noted above.
    • Replace ##LOGOUT URL## with the Logout URL Noted above.
    • Replace ##LOGIN URL## with the Login URL Noted above.
    • Replace ##CERTIFCATE## with the X.509 Certificate Noted above.
    • Set-MsolDomainAuthentication -Authentication Federated -DomainName ##DOMAIN NAME## -IssuerUri ##IDP ENTITY ID## -LogOffUri "##LOGOUT URL##" -PassiveLogOnUri "##LOGIN URL##" -SigningCertificate "##CERTIFICATE## -PreferredAuthenticationProtocol SAMLP
• You cannot federate your default "onmicrosoft.com" domain. To federate your Office 365 tenant, you must add a custom domain to Office 365.

Step 6: Now sign in to your Office 365 account with miniOrange IdP by either of the two steps:

1. Using SP initiated login :-

1. Login to your Office 365 account
2. Go to Office 365 Login
3. Enter only the Email. Now you will be redirected to miniOrange IdP Sign On Page.




4. Enter your miniOrange login credential and click on Login. You will be automatically logged in to your Office 365 account.




2. Using IdP initiated login :-

1. Login to your miniOrange Self Service Console as an End User and click on the Office 365 icon on your Dashboard.

Step 7: Configure 2FA for miniOrange Admin Dashboard and Office 365

7.1: Configure 2FA for miniOrange Admin Dashboard.

• From your miniOrange Dashboard in the left navigation bar, select 2- Factor Authentication, click on Configure 2FA.




• Choose any 2FA method you want to configure.
• Let's say you want to configure OTP over SMS
• Click on OTP over SMS





• Now add your mobile number on which you want to receive the OTP.
• Then click on Save.





• Now as shown in the above image, OTP over SMS is your Active 2FA method.
• Enable Prompt for second factor during signin to your console.
• Then click on Save.



• To verify the configuration login again.
• You will be asked for Username and password then it is redirected to below page:
• Enter the OTP received on the phone and click on verify.



• If you are redirected to your dashboard, you have successfully configured OTP over SMS as your 2FA method.
• Similarly you can configure rest of the 2FA methods for miniOrange dashboard. Click Here for the Guide
• To configure 2FA methods for end-users Click here.

7.2: Enable 2FA for Users of Office 365 application.

• To enable 2FA for Users of Office 365 application. Go to Policies >> App Authentication Policy
• Click on Edit against the configured application



• Enable the Enable 2-Factor Authentication (MFA) option.



• Click on Save.

Step 8: Adaptive Authentication with Office 365

8.1: Restricting access to Office 365 with IP Blocking

You can use adaptive authentication with Office 365 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 behaviour Change and Challenge Type for user from the Action for behaviour Change Section.





Action for behaviour Change Options :




Attribute	Description
Allow	Allow user to authenticate and use services if Adaptive authentication condition is true.
Challenge	Challenege 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 Notofication 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 recieve a OTP on the alternate email he has configured threw Self Service Conolse. 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.

8.2: 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 wii be able to access services provided by us on this fixed no. of devices.

You can cofigure Adaptive Authentication with Device Restriction in follwing way


• Login to Self Service Console >> Adaptive Authentication.
• Add a Policy Name for your Adaptive Authentication Policy.
• Select your Action for behaviour Change and Challenge Type for user from the Action for behaviour 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 Behaviour Change.)
1. Challenge: The user needs to verify himself using any of the three methods mentioned in table in step 8.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.

8.3: Add Adaptive Authentication policy to Google Apps (G Suite).

• Login to Self Service Console >> Policies.
• Click on Edit option for predefined SAML 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.




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.

For further details refer folowing Documents :

1. https://support.office.com/en-us/article/Office-365-integration-with-on-premises-environments-263faf8d-aa21-428b-aed3-2021837a4b65
   
2. http://blogs.technet.com/b/canitpro/archive/2015/09/11/step-by-step-setting-up-ad-fs-and-enabling-single-sign-on-to-office-365.aspx