Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Single Sign-On (SSO) is an account security feature that grants users access to applications. Referrers can go to the white-labeled login page and use the Single Sign On feature to login. To use single sign on, the Referrer must set up a domain with a provider. Identity Provider examples: OneLogin, Google, Microsoft and more.

Single Sign-On utilizes SAML 2.0 (Security Assertion Markup Language) or OpenID Connect protocols to authenticate a user and provide identity data for platform access control. This process allows authentication to be deferred to the IdP (Identity Provider).

See the expandable content below for a brief comparison of authentication protocols:

 Comparing SAML 2.0 & OpenID Connect 1.0

SAML 2.0

OpenID Connect 1.0

Supported Protocols

XML, HTTP, SOAP, & all other XML-friendly protocols.

XRDS & HTTP

Validation Process

Validated through chosen IdP intermediary service response.

Validated through OAuth server response.

Access Response

SAML authentication “assertion” is generated by the intermediary IdP service to grant access.

A temporary access token is granted by the IdP server to grant access.

Supporting Identity Providers

  • Okta

  • OneLogin

  • SalesForce

  • SiteMinder

  • Google

  • Microsoft

  • Okta

More info: Single Sign-On Auth Protocols

Visit the links below to learn more about different authentication protocols:

Getting Started with Single Sign-On

  • No labels