Reltio helps you to perform authentication operations for a user.


Authentication is the process or action of verifying the identity of a user or process. It is the act of validating whether users are who they claim to be. For example, to log in to an application, the user name and password entered are authencating factors. User is given access only if the correct data is entered.

In Reltio, the user has to obtain tokens to be able to access their tenants. The following topics help you to understand more about accessing tokens:

Authentication Features

Authentication features of Reltio Connected Cloud include:

  • Authentication Service
  • OAuth2 Single Sign On (SSO)
  • SAML Single Sign On (SSO)
Note: Reltio Connected Cloud also provides Authentication API, User Management API, and Role Management APIs with Authentication Service.

Authentication Scenarios

Specific authentication scenarios include:

Flexible Login Options for the User's Backend Implementation

When you log into Reltio platform, there are two options to log into the same or different tenants, depending on the tenant configuration:

  • SSO (Ping, Google): corporate IdP based
  • Non-SSO (Reltio Auth driven)

Users Sharing the Same Email

In Reltio, email address is a unique identifier for user identification. A user with an email address is given a specific set of roles. If another user is configured to access Reltio (for example, via OAuth2 Single Sign On (SSO)) with the same email address, then the user must not have the same set of roles as the already existing user. When the new user attemps to log in, the following error message is displayed:

This login is already in use by another customer. Please use a different account.

For different customers/tenants, it is recommended to set up and use accounts with different email addresses.