High Availability

In most environments there is requirement to have web-services running in an Active-Active or Active-Standby configuration.

This is easily accomplished by load-balancing or configuring fail-over between two or more instances of the Orbital Lite STS.

 

Considerations

A working STS installation can be copied to one or more servers. This reduces the required configuration on each instance.

External load-balancing via network load-balancer or similar device is recommended.

Keep in mind that each new instance will require a new license file. You can follow this process to generate the request so that Radius Works can provide you the file.

As part of the request processing a user’s information may be temporarily cached on the server when requesting authentication or obtaining a fetch. This means that to generate a SAML token, the client browser may actually process one or more requests to the STS in order to complete the process. Hence it is important the user’s request return to the same server.

If load-balancing, ensure that the affinity (“stickiness”) is set to the client IP. Keep in mind that in some environments behind a proxy or a NAT this may cause undue load. It should be noted that Orbital STS Lite uses SessionIDs that are available in the request header and stored via client-side cookie.