Skip to content
English
Contact us Customer portal
Our Website
  • There are no suggestions because the search field is empty.

Configure Okta SSO with Engagedly

Table of contents

  1. Introduction
  2. Configure SAML SSO in Engagedly
  3. Create app integration
  4. Configure IdP details in Okta
  5. Add IdP details to Engagedly

1. Introduction

Okta is a cloud-based identity and access management (IAM) platform that helps organizations securely manage user authentication and access to applications. It provides centralized identity management and enables secure access across cloud and on-premises environments.

Admins can integrate Okta with Engagedly to enable Single Sign-On (SSO), allowing employees to securely access Engagedly using their Okta credentials. This integration helps admins centralize authentication, strengthen security, reduce password-related issues, and simplify user and access management across the organization.

📒Note: Admins and users with integration permissions are authorized to configure this integration.

For more information about SSO integrations, refer to the Overview of integrations.

📒Note: This document covers the integration setup for both Tangerine (V2) and Indigo (V3). Screenshots are captured from Indigo (V3), so the user interface may vary slightly in Tangerine.

Prerequisites

2. Configure SAML SSO in Engagedly

Navigate to Settings > Integrations.

  1. In the ”SSO” field, click SAML Single Sign On.
  2. Click ADD at the top right.
  3. Enter an identifier name as required and click SAVE.

Configure Okta SSO with Engagedly1

Engagedly generates the ACS URL and Entity ID.

3. Create app integration

  1. Log in to the Okta Admin Portal.
  2. In the left panel, select Applications > Applications.
  3. Click Create App Integration.

Okta2

     4.  Select SAML 2.0 and click Next.

Okta3

     5.  Enter the app name as required.

     6. (Optional) Upload the app logo.

     7.  Click Next.

Okta4

4. Configure IdP details in Okta

  1. Copy the following values from Engagedly and paste them into the corresponding fields in Okta.
Engagedly field Okta field
ACS URL Single sign-on URL
Entity ID Audience URI (SP Entity ID)

     2.  Open the drop-down in “Name ID format” and select EmailAddress.

     3.  Open the drop-down in “Application username” and select Email.

Okta9

📒Note: Engagedly supports email address and employee ID formats only.

     4.  Select This is an internal app that we have created, and click Finish.

Okta10

     5.  Click More details to view "Issuer" and "Sign on URL".

Okta12

5. Add IdP details to Engagedly

  1. Copy the following values from Okta and paste them into the corresponding fields in Engagedly.
Okta field Engagedly field
Issuer Identity Provider Issuer
Sign on URL Identity Provider Single Sign-On URL

     2.  Click Download to download the certificate.

Okta17

     3.  Open the downloaded certificate in a text editor and copy the entire certificate, including the lines ----- BEGIN CERTIFICATE-----and----- END CERTIFICATE-----.

Okta18

     4.  Paste the certificate content into the ”Identity Provider X.509 Certificate” field in Engagedly.

     5.  (Optional) Click Test Connection to verify the setup.

     6.  Use the toggle to activate authentication using SAML and click SAVE.

Okta19

You have successfully configured Okta SSO with Engagedly.

After integration, assign the application to users or groups in Okta.

After assigning the application in Okta and adding users to Engagedly, users can access Engagedly using single sign-on (SSO).