Skip to main content

Okta SSO Integration (SAML 2.0)

Enable secure Single Sign-On for your organization using Okta.

Updated over 3 weeks ago

Overview

Empuls supports SAML 2.0–based Single Sign-On (SSO) via Okta, allowing employees to sign in using their corporate Okta credentials. This provides:

  • Seamless login experience

  • Centralized access management from Okta

  • Enhanced security with no passwords stored in Empuls

Once configured, users authenticate through Okta and automatically gain or lose Empuls access based on Okta assignments.

How It Works

With SAML 2.0, Okta acts as the Identity Provider (IdP) and Empuls acts as the Service Provider (SP).

Authentication flow:

  • User enters their email on the Empuls login page → clicks PROCEED

  • Empuls redirects the user to Okta

  • Okta verifies credentials

  • Okta sends a SAML response back to Empuls

  • User is granted access to Empuls

Set Up Okta SSO for Empuls

Prerequisites

Before you begin, ensure you have:

  • Admin access to Okta

  • Admin access to Empuls

  • Your Empuls tenant URL: https://{{tenant_url}}
    ​

A) Get Empuls SP Metadata

  • Log in to Empuls

  • Navigate to:
    ​Reports & Settings → Admin Dashboard → User Authentication → Custome Login SAML 2.0 SSO

  • Copy the following:

    • ACS URL

    • Entity ID

    • Name ID format

Or download the file: empuls-sp-metadata.xml

You'll use this in Okta.

B) Create the Empuls Application in Okta

https://developer.okta.com/docs/guides/build-sso-integration/saml2/main/

  1. Log in to the Okta Admin Console

  2. Go to Applications → Create App Integration

  3. Choose:

    • Sign-in method: SAML 2.0

    • Click Next

  4. Provide an App Name: Empuls

  5. In SAML Settings, enter:

General Settings

  • Single Sign-On URL: Empuls ACS URL

  • Audience URI (Entity ID): Empuls Entity ID

  • Name ID Format: EmailAddress

  • Name ID Value:

    • Select Email or Employee ID
      (must match Empuls user records)

6. Click Next, review settings, and save the application.

C) Assign Users to the Application in Okta

  1. Open the new Empuls app in Okta

  2. Go to Assignments

  3. Assign:

    1. Users

    1. or Groups

Only assigned users can log in to Empuls via SSO.

D) Export Okta Metadata & Upload to Empuls

Download from Okta:

  • Go to Applications → Empuls → Sign On

  • Click View SAML setup instructions

  • Download the IdP Metadata XML file

Upload to Empuls:

  • Go back to Empuls → User Authentication → SAML 2.0

  • Upload the IdP metadata XML at:

/home/integrations/saml_sso
​

E) Test the Connection

  • In Empuls, click Test Connection

  • A pop-up opens → ensure browser pop-ups are allowed

  • You are redirected to Okta

  • Log in with your Okta credentials

If successful → SSO is active and working.

F) Enable Okta SSO for All Users

To make Okta SSO the default login method:

Go to:
​Admin Dashboard → User Authentication → Custom Login Method → SAML 2.0 (Okta)

Troubleshooting

1. Test Connection fails

  • Ensure the Name ID is set to Email or Employee ID

  • Confirm the ACS URL and Entity ID match exactly

  • Reupload Okta metadata if updated

2. User assigned in Okta but cannot log in

  • Make sure the user exists in Empuls

  • Ensure the email/employee ID in Okta matches Empuls records

3. Pop-up blocked

  • Allow browser pop-ups for the Test Connection

Related Articles
Custom Login Method (SAML 2.0 Single Sign On/ SSO)
Azure AD
Empuls ADFS SSO Configuration
One Login Integration (SAML 2.0)
Ping Identity SSO Integration (SAML 2.0)
Did this answer your question?