The EmpowerID SSO framework allows you to federate EmpowerID with Office 365 without requiring you to setup ADFS or DirSync. In this scenario, the EmpowerID STS replaces ADFS, making EmpowerID the identity provider for your organization's Office 365 services.
As prerequisites to federating EmpowerID with Office 365, you must have a licensed corporate Office 365 account and have connected EmpowerID to Office 365. Additionally, you must have the following modules installed on the machine in which you are configuring the SSO Connection:
EmpowerID servers that will be connecting to Office 365 that currently have Windows Azure AD Module for Windows PowerShell and MSOL Sign-in assistant installed, will need to have those modules remove before installing the newer versions.
Windows Management Framework 5.0 - This framework provides updated management functionality that EmpowerID uses to communicate to Office 365, to include the newest version of Windows PowerShell. You can download the Windows Management Framework 5.0 from Microsoft at:
https://www.microsoft.com/en-us/download/details.aspx?id=50395. You must install the framework before installing Windows Azure AD Module for Windows PowerShell Version 1.1. Once you have installed the framework, you can verify the version by running $PSVersionTable.PSVersion in Powershell. The version returned should be Major 5 Minor 0 or higher.
Windows Azure AD Module for Windows PowerShell Version 1.1 - This provides you with the Office 365 cmdlets necessary for administering Office 365.
After installing Windows Azure AD Module for Windows PowerShell Version 1.1, run Save-Module -Name MSOnline -Path %path% in PowerShell, replacing %path% with the desired path. If you see messages stating that "PowerShellGet requires NuGet provider version'126.96.36.199' or newer" and "You are installing the modules from an untrusted repository", enter Y for both. Once completed, run Import-Module MSOnline in PowerShell. After importing the module, you can confirm you have the appropriate version by running Get-Module MSOnline. You should see version 188.8.131.52 returned.
This topic describes how to federate EmpowerID with Office 365 and is divided into the following activities:
Setting a Public DNS for your EmpowerID server. This is an optional step that is only required when the DNS for your server and the domain name you registered in Office 365 are not the same. (These values must match for SSL endpoints to function correctly.) By setting a DNS, you are directing the EmpowerID services to ignore the machine's FQDN and use the Public DNS in its place.
After connecting to Office 365, but before federating it with EmpowerID, it is recommended that the Office 365 users for the federated domain update their EmpowerID password. This is to ensure that their EmpowerID Person does not become locked out to a password mismatch between their EmpowerID Person password and an Office 365 password that is saved in rich client application such as Outlook or Lync.
To create an SSO application for Office 365
From the Navigation Sidebar, navigate to the find protected application resource page by expanding Applications and clicking Manage Applications.
From the Actions pane of Application Manager, click the Create Application action.
This opens the Application Details form, which contains various tabs and fields for creating the application.
From the General tab of the Application Details form, do the following:
Type an appropriate name, display name and description for the application in the Name, Display Name and Description fields, respectively.
Icon - Type ~/Images/AppLogos/office-365.png in this field. This is the path to the Office 365 image provided by EmpowerID. Users with access to the application will see this image representing Office 365 in their Personal Applications page of the EmpowerID Web application.
Full URL (Exact Match Path) - Leave this field blank as it is not used for Office 365.
Allow Access Requests - Specify whether to allow access requests. When this option is selected, the application appears in the IT Shop, allowing users to request or claim an account in the application.
Allow Claim Account - Specify whether to allow users to claim an account in the application from the IT Shop.
Allow Request Account - Specify whether to allow users to request an account in the application. When this option is selected and
Allow Access Requests is selected, users can request an account in the application.
Login Is Email Address (Receive OTP to Claim) - Select this option. This setting is necessary for passing the appropriate identity assertion to the application when logging in from EmpowerID and is used by EmpowerID to send a one-time password to users claiming an account.
Make me the Application Owner - Specify whether you are the owner of the application. Application owners have the ability to manage the application and approve or deny access requests.
Configure Advanced Claim and Request Account Options - If you have custom pages and workflows configured in EmpowerID for processing access requests as well as for managing any accounts linked the application's (internal to EmpowerID) account directory, then select this option and provide the appropriate information.
Click the Single Sign-On tab of the form, select WS-Federation from the Single Sign-On Connection Type drop-down and then tick Create a New WS-Fed Connection.
In the WS-Federation Connection Information section that appears, do the following:
Select Default SSO Connection Settings from the WSFederation Application Template drop-down.
Type Office365 in the Display Name field.
Type a description for the connection in the Description field.
In the Issuer field, type the value that best represents the issuer of your Office 365 WS-Fed connection, such as empowerid:mydomain.office365, substituting mydomain with your domain.
The value you place in the Issuer field is the same value that you will pass to Office 365 via PowerShell as the IssuerUri parameter. This value does not need to be a resolvable DNS; it just needs to be a value that you and Office 365 agree upon. Additionally, it needs to be unique in Office 365 as an IssuerUri cannot be used for more than one connection/tenant.
Type https://sso.empoweriam.com/EmpowerIDWebIdPWSFederation/Go365/Office365 in the Initiating URL field, where sso.empoweriam.com is the FQDN or DNS alias of your EmpowerID Web server and Office365 is the display name of the WS-Fed connection.
Type your domain in the Home Realm field.
In the Relying Party Trust section of the form, do the following:
Type urn:federation:MicrosoftOnline in the Absolute Uri field.
Select the certificate used to sign assertions from the Signing Certificate drop-down.
Click the Users tab and select the Office 365 account store you configured for your environment from the
Select existing Account Directory drop-down. EmpowerID uses this directory to map your Office 365 users with their corresponding EmpowerID Persons. Please note that you must add this account store to EmpowerID before it will appear in the drop-down.
Click Add to cart.
Click the shopping cart located at the top of the page and in the Cart dialog that appears, type a reason for creating the application and then click Submit.
After EmpowerID creates the application, click the Find Application link in the breadcrumbs at the top of the page.
Search for the Office 365 application you just created and then click the Display Name link for it .
This directs you to the View One page for the application. View One pages allow you to view and manage information about a particular resource object.
Expand the Owners accordion and do the following as needed to make someone an owner of the application. Owners have the ability to manage the application.
Type the name of the person who is to be the owner in the Enter name to add field and then click the tile for that person.
Expand the Who Has Access To Application accordion and do the following to ensure all users with an Office 365 account can access the application:
Select Business Role and Location from the Assignee Type drop-down.
Click the Add (+) button on the Assignee grid.
This opens the Grant Access dialog. You use this dialog to select the specific Business Role and Location for which you are granting access as well as the Access Level you are granting it.
In the Business Role pane of the Grant Access dialog, search for and select Any Role.
In the Location pane of the Grant Access dialog, search for and select Anywhere.
Log in to the EmpowerID Management Console as an administrator.
From the EmpowerID Management Console, click the EmpowerID logo and select Configuration Manager from the menu.
In Configuration Manager, expand the EmpowerID Servers and Roles node in the application navigation tree and then click EmpowerID Servers.
From the Configuration Manager grid, search for the EmpowerID server for which you wish to add the public DNS alias.
Double-click the record for the target server.
In the EmpowerID Server Details screen that appears, type the DNS alias in the Public Dns field and click Save.
The value entered here must be found in the SSL Certificate (i.e., Subject Name, SAN Cert, etc.).
Restart the EmpowerID services on that server.
To export the EmpowerID Certificate in base64-encoding format
From the server with your certificate, open the console root with the certificates snap-in (usually named Console 1). If you do not have the console configured with the certificates snap-in, open MMC and add the snap-in.
From Console 1, expand the Certificates (Local Computer) > Personal nodes and then click Certificates.
From the Personal certificates store, right-click the certificate you are using in your EmpowerID deployment and select All Tasks > Export from the context menu.
In the Certificate Export Wizard that appears, click Next.
Select No, do not export the private key and click Next.
Select Base-64 encoded X.509 (.CER) and click Next.
Select an export location, naming the exported certificate accordingly and click Next.
Click Finish to complete the export.
Open the exported certificate in a text editor and remove the first and last lines (----BEGIN CERTIFICATE----
and ----END CERTIFICATE----).
Remove all spaces and line breaks so that the certificate appears on one line.
Next, establish trust between Office 365 and EmpowerID as described below.
To establish trust between Office 365 and EmpowerID
From the Start menu, open the Windows Azure AD Module for Windows PowerShell command window and type Connect-MsolService in the command window to connect to Microsoft Online.
In the Enter Credentials window that appears, type the username and password for a global administrator and click OK.
Once you have connected, run the following command to set the ImmutableID on all Office 365 accounts that have the domain specified in the command. Be sure to replace YourDomainName with your domain name.
This command is only necessary if the account was created in Office 365.
Next, set the following variables at the PowerShell prompt for your domain, the federation endpoints and the signing certificate. The following example shows what the values for the variables looked like for our configuration. You need to replace the values with those specific to your environment. For example, the name of our domain is "myempowerid.com," so the value of $dom and $FederationBrandName is "myempowerid.com."
The values for the ActiveLogOnUri, LogOffUri, and PassiveLogOnUri are the same and point to the Issuer you set up when you created the WS-Fed connection above. The value set for the IssuerURI does not need to be a resolvable DNS; however, it does need to be unique in Office 365 as an IssuerURI cannot be used for more than one connection/tenant . Also, when setting the value for the certificate, be sure to pass in the string without any line breaks, using Base-64 encoding.
If you received a DefaultDomainUnsetException error when running the above PowerShell cmdlet, you need to specify the domain as the default domain. To fix the error run the below cmdlet. Additionally, you will need to run the cmdlet each time you add a tenant to set the default domain for those tenants. Be sure to replace "empowerid.onmicrosoft.com" with the fully qualified domain name your Office 365 account was given by Microsoft when first created.