Table of contents
1. Introduction
Okta is a cloud-based identity and access management (IAM) platform that simplifies secure access to applications for employees. It provides single sign-on (SSO), allowing employees to log in once and access multiple applications without needing to remember separate credentials for each. Okta also offers features like multi-factor authentication (MFA) and user provisioning to help organizations manage and protect their users' access to applications securely.
The Okta and Engagedly integration allows employees to use their Okta credentials to access Engagedly, providing a seamless and secure single sign-on (SSO) experience. IT teams can efficiently manage user access and permissions, ensuring that only authorized users can access sensitive data. By centralizing identity management, organizations can improve security, reduce administrative overhead, and offer a smoother user experience across platforms.
2. Integration
Admins can seamlessly set up SSO using Okta with Engagedly, which enhances security and simplifies identity management for organizations.
Note: Admins and users with integration permissions can integrate the applications.
Prerequisites
- Subscription to Okta and Engagedly.
Navigate to Settings > Integrations.
- In the SSO field, click SAML Single Sign On.
- In the SAML SSO window, click ADD at the top right.
- In the ADD SAML SSO pop-up, type the identifier name and description as required and click SAVE at the bottom.
Once saved, the system will generate the ACS URL and Entity ID.
4. Log in to your Okta account.
5. On the left pane, select Applications, then select Applications, and click Create App Integration.
6. Select SAML 2.0 and click Next.
7. Type the app name as required, upload the app logo, which is optional, and click Next.
8. Navigate to Engagedly and copy the ACS URL and Entity ID.
9. Navigate to Okta and paste the ACS URL and Entity ID into the Single sign-on URL and Audience URI (SP Entity ID) fields, respectively.
10. Click the drop-down in the Name ID format field and select EmailAddress.
Note: If your organization uses an email address or employee ID, select the appropriate option in the Name ID format field.
11. Click the drop-down in the Application username field, select Email, and click Next.
12. Select the option This is an internal app that we have created and click Finish.
13. Click More details to view Issuer and Sign on URL.
14. Navigate to Engagedly, click the Overflow 
Menu, and select Edit to configure SAML for Okta.
15. Navigate to Okta and copy the Sign on URL and Issuer URL.
16. Navigate to Engagedly and paste the Sign on URL and Issuer URL into the Identity Provider Single Sign-On URL and Identity Provider Issuer fields, respectively.
17. Click Download to download the certificate.
18. Open the downloaded certificate in a text editor and copy the entire certificate, including the lines ----- BEGIN CERTIFICATE-----and----- END CERTIFICATE-----.
19. Navigate to Engagedly and paste the certificate content into the Identity Provider X.509 Certificate field.
20. Toggle the button to activate authentication using SAML and click SAVE.
Okta is successfully integrated with Engagedly for single sign-on (SSO).
After integration, you must assign the application to users or groups in the Okta portal.
After assigning the application in Okta, and adding users to Engagedly, users can access Engagedly using single sign-on (SSO).