Versions Compared

Key

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

Modern authentication with Azure AD

With Modern Authentication, users authenticate with OpenID Connect against the customer’s own Azure tenant using a browser. This means that user accounts are centralized to the customer’s own Azure and are by definition subject to the already-existing security policies.

Tenant configuration

To enable Azure AD authentication integration to Enreach Voice services, two Enreach Voice enterprise applications must be consented by the customer’s Azure tenant administrator:

  • EnreachVoice application

    • Enables the users to sign in via Enreach Identity

  • EnreachVoice UserSync application

    • Enables Enreach backend to read and synchronize user information from Azure. This is needed to correlate users in Enreach system to Azure users.

Consent is granted by generating the following two links pointing to the customer tenant.

  • https://login.microsoftonline.com/<tenant-id>/adminconsent?client_id=a289977d-5d74-48c9-865c-29705346e99d

  • https://login.microsoftonline.com/<tenant-id>/adminconsent?client_id=633f3578-9b28-493a-91f2-1edfdc069a7a

After generating the links by populating the correct tenant id, a tenant Global Global administrator follows the links and grants the consents in Azure.

Image RemovedImage Removed

Classic authentication

In classic modeMore details and step-by-step instructions on how to configure modern authentication with AzureAD are here: Enabling SCIM integration with Azure AD

Classic authentication integration with AzureAD

Note

Classic authentication mode is maintained for backwards compatibility. All new deployments are done using Modern Authentication.

In classic authentication integration, user credentials are passed through the Enreach backend to Azure for validation. This mode is maintained for backwards compatibility - new deployments focus on Modern Authentication.

To enable classic Azure AD Authentication integration for your organization, an Azure AD application must be registered to the customer Active Directory in Azure management portal. 

...

5. Go to Authentication tab and configure following

  1. Select “Add a platform”

...

  1. Image Added
  2. Select Web

...

  1. Image Added
  2. Configure Web

    1. Enter https://api.beneservices.com as RedirectURI

    2. Select ID Tokens

    3. Click Configure

      Image Modified
  3. Set Allow public client flow = Yes

...

  1. Image Added

  2. Click Save


6. Go to Permissions tab

  1. Make sure that app have User.Read permission

...

  1. Image Added


  2. Click Grant admin consent and Yes to confirmation

    Image Modified

  3. Make sure that there is a green mark for Admin consent

    Image Modified

8. Go to Overview tab

  • Send Application ID value to Enreach

...