This documentation supports the 19.11 version of BMC Remedy Single Sign-On, which is available only to BMC Helix subscribers (SaaS).To view an earlier version, select the version from the Product version menu.

Remedy SSO multitenancy

Remedy Single Sign-On is supported in multitenancy mode where a single application instance serves multiple tenants and guarantees data isolation between tenants. In a multitenant mode, each tenant has its own configuration with its own list of realms, settings related to the cookie name, OAuth client, sessions, administrator users, etc.  

As a SaaS administrator,  you might need to configure multiple tenants for Remedy SSO to isolate data within a single instance of Remedy SSO.

Related topics

Roles-and-permissions

Activating-tenants

The following diagram illustrates the concept of multitenancy in Remedy SSO:

RSSO multitenancy.png

Tenants in this diagram represent Remedy SSO configuration instances which are isolated  from each other, but are physically saved on the same  Remedy Single Sign-On server.

A SaaS tenant is the predefined tenant available on the Remedy SSO server.  The SaaS tenant cannot be deleted or modified. We do not recommend using the SaaS tenant for data segregation. 

Tenant 1 and Tenant 2 are customer tenants created by a SaaS administrator user. Tenant 1 administrator user can log in to the Admin Console of Tenant 1 and make changes to its configuration, and Tenant 2 administrator user can login to the Admin Console of  Tenant 2 and make changes to its configuration. The SaaS administrator user can set up configuration for any tenant on the Remedy SSO server by switching to the Admin Console of a  selected tenant. 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*