This documentation supports the 18.05 version of Remedy Single Sign-On.

To view the latest version, select the version from the Product version menu.

Deployment scenarios

You can deploy the Remedy Single Sign-On web application in the following ways to accommodate a range of conditions and use cases:

Standalone environment

You can deploy the Remedy SSO on a standalone server. In this scenario, Remedy SSO is installed on a single server. 

HA environment

To implement Remedy SSO as a redundant system with session failover, you can deploy the Remedy SSO in an HA mode. In an HA environment, multiple instances of the Remedy SSO server are deployed. Usually, a load balancer is used as a front end of the HA mode, giving the external applications the appearance of a single server. The load balancer distributes requests among Remedy SSO nodes. Remedy SSO does not require sticky sessions, so requests can be handled by any instance.

When multiple Remedy SSO servers are installed and configured to operate in an HA environment, if one of the HA nodes fails, the system failure is absorbed by the remaining nodes with minimal interruption. No additional configuration is required on the Remedy SSO side as each node is unaware whether it works in HA mode or not. All HA mode configuration is done externally by using the network infrastructure.

In an HA environment, Remedy SSO functions as a single virtual server. Therefore, all configuration information, user sessions data, and user tokens are stored in a single database and shared (not replicated) between nodes. To prevent the database from becoming a single point of failure, database replication may be required, but the specific settings depend on the specific environment. Therefore, database replication is out of scope of the Remedy SSO documentation.

Where to go from here

Security planning

Was this page helpful? Yes No Submitting... Thank you