This documentation supports the 20.08 version of 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.

Connecting the same Remedy SSO agent to different Remedy SSO servers

The Remedy SSO agent is usually configured to communicate with only one Remedy SSO server.  In such configuration, the  Remedy SSO agent performs tasks, such as checking configuration, checking the single sign-on token, and redirecting logons and logoffs.

Related topics

Remedy-SSO-agent
Configuring-Remedy-SSO-agent

You can configure the Remedy SSO agent to support communication with multiple Remedy SSO servers on different domains.

Multiple servers on different domains.png

The mapping between a domain and a Remedy SSO server (<domain>:<url>) is defined through the sso-external-url and sso-service-url properties in the rsso-agent.properties file.

To support multiple Remedy SSO servers on a single Remedy SSO agent, set different values of the domain-to-server mapping as comma-separated strings.

In the following configuration example,  firstcompany and secondcompany are the Remedy SSO servers' domains, and firstcompany-hsso.bmc.com and secondcompany-hsso.bmc.com are the Remedy SSO servers URLs:

sso-external-url=firstcompany:https://firstcompany-hsso.bmc.com:8443/hsso,secondcompany:https://secondcompany-hsso.bmc.com:8443/rsso
sso-service-url=firstcompany:http://firstcompany-hsso.bmc.com:8080/hsso,secondcompany:http://secondcompany-hsso.bmc.com:8080/rsso


 

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