Unsupported content This version of the product is in limited support. However, the documentation is available for your convenience. You will not be able to leave comments.

Connecting Remedy SSO agent to multiple 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

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

RSSO_Multiple Servers_ver4.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, you must 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 server domains, and firstcompany-rsso.bmc.com and secondcompany-rsso.bmc.com are the Remedy SSO server URLs:

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


 

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