Concept: Single Sign-On
Background
You can use Security Assertion Markup Language (SAML) for single sign-on (SSO) in Peakon. Example: Users with manager and personal dashboard access can sign in with their existing company identity without requiring separate sign-in credentials for Peakon.
Peakon integrates with any external system capable of acting as a SAML 2.0 identity provider.
SAML is a standard for exchanging authentication and authorization data between security domains. It enables administrators to manage user credentials centrally through a third-party identity provider (IdP). Example: Okta. Once configured, users can access Peakon directly from the organization's central app portal.
Users can initiate sign-in from service provider websites and from app portals of identity providers.
Popular hosted services with SAML support include, but are not limited to:
- G Suite (Google Apps)
- Microsoft ADFS
- Microsoft Entra
- Okta
- OneLogin
Considerations
Users who access their dashboards for the first time using their email confirmation link, will gain access without having to authenticate using SSO for the first time only. All subsequent logins require authentication via SSO.
Contact Customer Care if your organization uses multiple email domains so they can add them as supported domains to your organization's account.
Employee email addresses must be an exact match to the email address on the organization's identity provider. Consider this if your organization uses email aliases.
Recommendations
- Set theRequire single sign-onsetting toEveryoneif you want to ensure that all users authenticate through SSO only.
Limitations
- Only Peakon administrators can access SSO configuration on Peakon.
- It's not possible to add common email domains on your Peakon account for SSO. Example. @gmail.com.
- You can't include singing and encryption certificates on the XML metadata. Peakon only supports encryption.
- Peakon requires a SessionIndex-attribute on the AuthnStatement-element of the SAML assertion provided by an IdP.