Breadcrumbs

Single Sign On: Accounts

Engaging Networks supports Single Sign-On (SSO) integration with Microsoft Entra ID (formerly Azure AD) and Okta using the OpenID Connect (OIDC) protocol. This allows your team to authenticate into the Engaging Networks platform using their existing corporate credentials, enhancing security and simplifying user management.

Entra Integration

Before you begin

To complete this setup, you will need:

  • Administrative access to your organization’s Microsoft Entra admin center.

  • Account Administrator permissions in Engaging Networks.

  • Your Engaging Networks Client ID (Hello > Client ID).

Step 1: Configure Microsoft Entra ID

First, you must register Engaging Networks as an application within your Microsoft Entra ID tenant.

  1. Sign in to the Microsoft Entra admin center.

  1. Navigate to Identity > Applications > Enterprise applications and select New application.

  1. Select Create your own application. Enter a name (e.g., “Engaging Networks SSO”) and choose Register an application to integrate with Microsoft Entra ID (App registrations).

  1. Under Supported account types, select the option that fits your organization (typically “Accounts in this organizational directory only”).

  1. In the Redirect URI section, select Web and enter your Engaging Networks callback URL: https://[your-server-base-url]/ea-dataservice/rest/account/auth/client/[your-client-id]

  1. After registration, navigate to Certificates & secrets and create a new Client secret. Copy the Value immediately, as it will be hidden later.

  1. Navigate to the Overview page and copy the Application (client) ID and the Directory (tenant) ID.

Step 2: Enable the Entra ID Extension in Engaging Networks

Once the application is registered in Microsoft, you must provide the credentials to Engaging Networks to complete the link.

  1. Log in to Engaging Networks and navigate to Account Settings > Extensions.

  1. Locate the Microsoft Entra ID extension and select Setup.

  1. Set the Status to Enabled.

  1. Enter the Base URL using your Tenant ID: https://login.microsoftonline.com/[your-tenant-id]

  1. Enter the External Client ID (the Application ID from Entra ID).

  1. Enter the Client Secret generated in Step 1.

  1. Select Save to apply the changes.

Important Notes

  • Client Secret Management: You do not need to re-enter the Client Secret when updating other settings in the extension. However, if you generate a new secret in Entra ID, you must update it here to maintain the connection.

  • User Access: Ensure that users who need to log in via SSO are assigned to the application within the Microsoft Entra admin center.

  • Login URL: Once configured, users can initiate login via the standard Microsoft OIDC flow or a direct login URL formatted for your account.

Okta Integration Overview

The Okta integration uses the Open ID framework to allow authenticated users to securely log in to an individual account. 

Clients using the Accounts Hub may also enable the Okta integration through this process, using a separate Okta app. Okta can also be used to allow your supporters to log into the Supporter Hub – see the separate documentation if you wish to use it there. The Supporter Hub implementation also requires a separate Okta app.

Set Up Instructions

  1. In Okta, click on Add Application

    okta-1-add-application.png

  2. Choose OpenID Connect 

    okta-2-openid.png

  3. Give the application a name, e.g. “Engaging Networks Okta Accounts”

    okta-3-name.png

  4. The web app redirect URI should point to one of the URLs below depending on your server. The ClientID can be found in Engaging Networks under the Hello menu.

CA

https://ca.engagingnetworks.app/ea-dataservice/rest/account/auth/client/{clientId}

US

https://us.engagingnetworks.app/ea-dataservice/rest/account/auth/client/{clientId}

US2

https://us2.engagingnetworks.app/ea-dataservice/rest/account/auth/client/{clientId}

  1. On saving, Client ID and Client Secret keys will be generated.

  2. Edit the General settings and add Initiate login URI – https://ca.engagingnetworks.app/index.html#login or https://us.engagingnetworks.app/index.html#login or
    https://us2.engagingnetworks.app/index.html#login

  3. Add ‘People’ under Directory. Make sure that these users exist in Engaging Networks

  4. In Engaging Networks, enable the Okta integration in your Engaging Networks account by navigating to the Extensions Manager under your Account Settings. Select the Okta integration available under the Account level integration options. 

    Okta-Integration.jpg

    The Page level Okta integration allows enabling with the Supporter Hub.

  5. Enter the required details prompted, including Okta Client ID and Client Secret (this should be used from your web app in Okta). The Okta login URL should be auto-populated in Engaging Networks. Be sure to save all details updated to enable.

  6. Update your web app in Okta with the login URL populated.

  7. In the Okta web app, Add users under ‘Assignments’ in the web app with a primary email address for each. This will determine who is able to access the particular account (or associated subaccounts).

  8. When the redirect is sent to Engaging Networks, it will make the appropriate calls to obtain the access token. Using the access token, Engaging Networks will make a call to the ‘userinfo’ endpoint to obtain the email address of the authenticated user. It will then use that email address to log the user into the account.

Note: When a user logs out of the account, Engaging Networks will destroy the application session but will not log the user out of Okta.