EmpowerID can be configured to allow enable users to authenticate to EmpowerID and using their Azure credentials and access EmpowerID, as well as single sign-on (SSO) into other applications to which where EmpowerID serves functions as an the Identity Provider using their Azure credentials(IdP). Once a user authenticates and does , they can use SSO to other access Service Provider applications such as like Salesforce or ServiceNow, that user can seamlessly sign out of all applications simply by signing out of one. The flow for both of these scenarios looks as follows:Login Scenario – The user goes to SP1 and lands on the EmpowerID Login page for authentication. The user selects Azure Native Auth. Subsequently, the user performs single sign-on , streamlining the login experience. Additionally, EmpowerID supports seamless single logout (SLO), allowing users to sign out of all connected applications by logging out from any one of them.
Flow Overview
Login Scenario
The user navigates to Service Provider 1 (SP1) and is redirected to the EmpowerID login page.
The user selects Azure Native Authentication and logs in using their Azure credentials.
Once authenticated, the user can perform SSO into SP1, SP2, and SP3 without additional logins.
Logout Scenario
– TheWhen the user logs out of SP1 and multiple from SP1, a series of coordinated logout requests /responses are exchanged between EmpowerID, Azure Multi-tenant IDP and the service providers.
The single log out flow from the above image is as followsand responses ensure that the user is logged out from all applications. The steps involved in this process are:
SP1 sends a logout request to EmpowerID.
EmpowerID sends a logout request to Azure.
Azure sends a logout response back to EmpowerID.
EmpowerID sends a logout request to SP2.
SP2 sends a logout response to EmpowerID.
EmpowerID sends a logout request to
SP3.
SP3 sends a logout response to EmpowerID.
EmpowerID sends a final logout response to SP1, completing the process.
| Easy html macro | ||||
|---|---|---|---|---|
| ||||
Procedure
Step 1 – Set up Azure Native Auth
On the navbar, expand Apps and Authentication > SSO Connections and click OAuth / OpenID Connect.
Select the External OAuth Services tab and then search for AzureAD.
Click the Provider link for AzureAD.
This directs your browser to the View One page for the AzureAD External OAuth Provider.
If you are not using EmpowerID SaaS do the following:
On the View One page, click the Edit link for the AzureAD Provider.
Replace the default values for the below endpoints with those you copied for your Azure app registration in the above Prerequisites steps.
Authorize URL (V1) – Replace the default with the OAuth 2.0 authorization endpoint (V1) for your Azure app
Request URL – Replace the default with the OAuth 2.0 token endpoint (V1) for your Azure app
Login URL (V2) – Replace the default with the OAuth 2.0 authorization endpoint (V2) for your Azure app
Access URL – Replace the default with the OAuth 2.0 token endpoint (V2) for your Azure app
Logout URL – Replace the default with
https://login.microsoftonline.com/<TenantID>/oauth2/v2.0/logout?post_logout_redirect_uri={0}(Replace <TenantID> with your tenant's ID.)
Save your changes.
Back in the View One page, click the Edit button for the AzureAD record in the grid.
If you are not using EmpowerID SaaS, do the following:
Update the Consumer Key field with the Application (client) ID of the Azure app registration you created in the above Prerequisites steps.
Update the Consumer Secret field with the Secret ID of the secret you created for the Azure app registration in the above Prerequisites steps.
Update the Callback Url field with the FQDN of your EmpowerID server. The value entered should look similar to
https://sso.empoweriam.com/WebIdPForms/OAuth/V2, wheresso.empoweriam.com, is the FQDN of the EmpowerID web server in your environment.
Click Save.
On the navbar, expand Admin > Miscellaneous and click Lists.
From the Lists tab, search for Whitelisted and then click the Display Name link for the Azure Multi-Tenant Whitelisted Domains record.
Expand the Items accordion and then click the Add button in the grid header.
Add your domain as a List Item. Enter the domain name in all three fields.
Click Save.
On the navbar, expand Admin > Applications and Directories and click Account Stores and Systems.
Search for AzureGlobalIdP and then click the Account Store link for the record.
On the Account Store Details page that appears, click the Edit link to put the account store in edit mode.
From the Settings tab of the Edit Account Store page, go to the Provisioning Settings pane and locate the Default Person Business Role and Default Person Location settings.
Under Default Person Business Role, click the Select a Business Role link and then search for and select the desired Business Role for the Person objects EmpowerID provisions from the account store.
Click Save.
Under Default Person Location (leave blank to use account container, click the Select a Location link and then search for and select the desired location for the Person objects EmpowerID provisions from the account store.
Click Save.
| Info |
|---|
If you want to configure domain specific Business Role and Location allocation for the people EmpowerID provisions, please follow the below steps. |
Sep 2 – Configure domain-specific Business Role and Locations
On the navbar, expand Admin > Miscellaneous and click Lists.
From the Lists tab of the find ListDataItemSet page that appears, search for FQN and then click the Display Name link for FQN to BusinessRoleLocationMapping.
On the ListDataItemSet page, expand the Items accordion and click the Add button on the grid header.
In the List Items pane, add the following information:
Name / Key – Name of your domain
Display Name – Display name for your domain
Value – The OrgRoleOrgZoneID of the Business Role and Location combination in which you want people to be placed in.
Click Save.
Step 3 – Add a Login Button for Azure Native Authentication
On the navbar, expand Single Sign-On > SSO Connections and click SSO Components.
Select the IdP Domains tab and then click the IdP Domains link for the IDP Domain where you want the Login button to appear.
Select the External OAuth Providers tab and then select the Azure Native Authentication provider.
Click Save.
| Tip |
|---|
If a global administrator logs in using the Azure Native Authentication, the Azure consent prompt will include a checkbox “Consent on behalf of your organization”. If you check this option, the app will not prompt any other users in the organization to review the permissions; otherwise, all users in the organization will be prompted to review the permissions. |
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| Div | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
IN THIS ARTICLE
|