Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

EmpowerID can be configured to allow users to authenticate to EmpowerID and single sign-on (SSO) into other applications to which EmpowerID serves as an Identity Provider using their Azure credentials. Once a user authenticates and does SSO to other Service Provider applications such as 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 into SP1, SP2 and SP3.

...

Image Added

Logout Scenario — The user logs out of SP1 and multiple logout requests/responses are exchanged between EmpowerID, Azure

...

Multi-tenant IDP and the service providers.

...

Image Added

The single log out flow from the above image is as follows:

  1. SP1 sends logout request to EmpowerID.

  2. EmpowerID sends logout request to Azure.

  3. Azure sends logout response to EmpowerID.

  4. EmpowerID sends logout request to SP2.

  5. SP2 sends logout response to EmpowerID.

  6. EmpowerID sends logout request to SP2.

  7. SP3 send logout response to EmpowerID.

  8. EmpowerID sends logout response to SP1.

Note

Prerequisites

To complete this process, you will need the Azure domain to configure the Callback URL setting. See your EmpowerID Azure administrator for this information.

...

Set up Azure Native Auth

  1. On the navbar, expand Single Sign-On > SSO Connections and click OAuth / OpenID Connect.

  2. Select the External OAuth Services tab and then search for AzureAD.

  3. Click the Provider link for AzureAD.

    Image Modified

  4. Click the Edit button for AzureAD.

    Image Modified

  5. 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, where sso.empoweriam.com, is the FQDN of the EmpowerID web server in your environment.

    Image Modified

  6. Click Save.

  7. On the navbar, expand Admin > Miscellaneous and click Lists.

  8. From the Lists tab, search for Whitelisted and then click the Display Name link for the Azure Multi-Tenant Whitelisted Domains record.

    Image Modified

  9. Expand the Items accordion and then click the Add button in the grid header.

    Image Modified

  10. Add your domain as a List Item. Enter the domain name in all three fields.

...

  1. Image Added

  2. Click Save.

  3. On the navbar, expand Admin > Applications and Directories and click Account Stores and Systems.

  4. Search for AzureGlobalIdP and then click the Account Store link for the record.

    Image Modified

  5. On the Account Store Details page that appears, click the Edit link to put the account store in edit mode.

    Image Modified

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

    Image Modified

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

  8. Click Save.

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

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

...

Configure domain specific Business Role and Locations

  1. On the navbar, expand Admin > Miscellaneous and click Lists.

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

    Image Modified

  3. On the ListDataItemSet page, expand the Items accordion and click the Add button on the grid header.

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

      Image Modified

  5. Click Save.

Add a Login Button for Azure Native Authentication

  1. On the navbar, expand Single Sign-On > SSO Connections and click SSO Connections.

  2. Select the IdP Domains tab and then click the IdP Domains link for the IdP Domain where you want the Login button to appear.

    Image Modified

  3. Select the External OAuth Providers tab and then select the Azure Native Authentication provider.

    Image Modified

  4. 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
IL:External Stylesheet
IL:External Stylesheet
nopaneltrue

Div
stylefloat: left; position: fixed;

IN THIS ARTICLE

Table of Contents
maxLevel4
minLevel2
stylenone