One login for everyday access
Employees reach Empuls with the same OneLogin credentials they use for other work apps. Fewer passwords to remember and reset.
Let employees sign in to Empuls with their OneLogin credentials over SAML 2.0.
Get a personalised walkthrough. We respond within one business day.
What you can do
OneLogin handles identity. Empuls accepts the sign-in, so access follows the rules your IT team already manages.
Use cases
Three ways teams use OneLogin SSO with Empuls.
Employees reach Empuls with the same OneLogin credentials they use for other work apps. Fewer passwords to remember and reset.
Make SSO mandatory once your rollout is complete, so every sign-in to Empuls goes through OneLogin.
Your identity team continues to manage authentication in OneLogin, with Empuls added as one more SAML 2.0 application.
How it works
In the OneLogin Admin Portal, create a new SAML 2.0 application for Empuls.
Enter the ACS URL and Entity ID (Audience URI) from Empuls, then set the NameID format and attribute mapping.
Download the OneLogin IdP metadata and upload it in the Empuls admin settings.
Run a test sign-in, then choose whether SSO is optional or mandatory for your organization.
Setup
Your admin configures a SAML app in OneLogin and uploads its metadata to Empuls.
Native SSO integration for Empuls using OneLogin.
SAML 2.0. Sign-in is initiated from the Empuls email prompt and redirected to OneLogin.
Email (recommended), or Unspecified using Employee ID.
ACS URL and Entity ID / Audience URI. Default Relay State is optional.
Common questions from IT admins and security reviewers evaluating OneLogin 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