About Single Sign-On (SSO) User Authentication

This page provides a general explanation of the Single Sign-On (SSO) user authentication type. To see details on how to configure a portal with SSO, go to the article Configuring SSO as Authentication Type.  

What is SAML?

SAML (Security Assertion Markup Language) is the most widely used form of Single Sign-On (SSO) user authentication in the world. SAML allows end-users to access multiple, independent systems without having to login separately for each one. Perhaps you have used the “Login with Google” option to access different apps that you use regularly like Netflix or Zoom? If you have done this, you were using the SSO method, which allowed you to access the service you wanted with the credentials provided by Google that proved that you were you.

If you choose SAML 2.0 for a portal, you will need to follow all integration and configuration steps—once you’ve set it up, you will have provided your members with a very convenient means of accessing the Engagement Rx system.

How does SAML 2.0 work?

There are three main roles in SAML integration:

1. The Principle—This is the end-user, your members, who will be accessing the Engagement Rx system after they’ve been validated behind the scenes by the IdP.


2. The IdP—This is the Identity Provider; it is the system that is responsible for authenticating the identity of a user (in other words, when the user wants to log on, it is this party that makes sure they are supposed to have access to the system). This is the integrating partner (or client) to Engagement Rx. This is you.


3. The SP—This is the Service Provider (Engagement Rx); it is the system that provides the requested resource to the end-user after their identity has been validated by the IdP. 

SAML 2.0 makes it so your members do not have to sign on to the Engagement Rx system separately. Instead, your members will automatically have access to the Engagement Rx system when they are logged into your system.