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: Add On-Premise Active Directory as a User Store in miniOrange

Single Sign-On into Office 365 requires connection to an on-premise Active Directory. miniOrange allows on-the-fly user creation from Active Directory, negating the need for sync operations.

• Login to miniOrange Admin Console.
• Navigate to the User Stores section.
• Click on the Add User Store button.
• Select User Store 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.
  
  



• Insert follwing values in respective fields.
  
  

  Directory Type:	Active Directory
  LDAP Server URL:	Your AD server URL or IP address
  Bind Account DN:	Please perform below steps
  Bind Account Password:	Please perform below steps
  Search Bases:	Please perform below steps
  Search Filter:	Please perform below steps

• Go to AD FS-> Domain-> respective Users -> Properties-> Attribute Editor. Now copy the value of distinguishedName and paste it against Bind Account DN.



• Enter the valid password for the user from above step.
• Search Base is a user search location. It means where to search for a user.



• If you want to add extra conditions on user search you can add it in Search Filter. If you are not sure what to add, then add (&(objectClass=*)(cn=?)).



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

  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

• Click on Save.

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.1Configure Single Sign On (SSO) Settings

• Login to miniOrange Admin Console.
• Go to Apps >> Manage Apps . Click Configure Apps button.
• Click on SAML tab. Select Office365 and click Add App button.



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

Using Two Factor Authentication for Office 365

The most practical way to strengthen authentication is to require a second factor after the username/password stage. Since a password is something that a user knows, ensuring that the user also has something or using biometrics thwarts attackers that steal or gain access to passwords.

Traditional two-factor authentication solutions use hardware tokens (or "fobs") that users carry on their keychains. These tokens generate one-time passwords for the second stage of the login process. However, hardware tokens can cost up to $40 each. It takes time and effort to distribute them, tracks who has which one, and replace them when they break. They're easy to lose, hard to use, and users consistently report high levels of frustration with token-based systems.

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