One login for everyday access
Employees reach Empuls with the same Ping Identity credentials they use for other work apps. Fewer passwords to remember and reset.
Let employees sign in to Empuls with their Ping Identity credentials over SAML 2.0.
Get a personalised walkthrough. We respond within one business day.
What you can do
Ping Identity handles identity. Empuls accepts the sign-in, so access follows the rules your IT team already manages.
Use cases
Three ways teams use Ping Identity SSO with Empuls.
Employees reach Empuls with the same Ping Identity credentials they use for other work apps. Fewer passwords to remember and reset.
Route every Empuls sign-in through Ping Identity so access follows the policies your security team already enforces.
Your identity team continues to manage authentication in Ping Identity, with Empuls added as one more SAML application.
How it works
In Empuls, go to Reports and Admin, then User Authentication, and obtain the service provider metadata.
In the Ping Identity Admin Console, add a new Web App with SAML under Connections, then import the metadata or enter the ACS URL and Entity ID.
Map NameID to the email address, enable the app, download the IdP metadata from Ping Identity, and upload it to Empuls.
Click Test Connection in Empuls and confirm the Ping Identity login succeeds.
Setup
Your admin configures a SAML web app in Ping Identity and uploads its metadata to Empuls.
Native SSO integration for Empuls using Ping Identity.
SAML 2.0.
A unique identifier: Email ID or Employee ID. SAML_SUBJECT maps to the email address.
ACS URL, Entity ID, or the SP metadata XML file from Empuls.
Common questions from IT admins and security reviewers evaluating Ping Identity SSO for Empuls.
Still have a question? Talk to usA 30-minute call. We'll walk through the SAML settings, NameID options, and how to roll out SSO to your organization.
Book a demo