Autoscaling on Access gateway Servers


Article ID: 194925


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On Agents (SiteMinder) CA Single Sign On Federation (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) SITEMINDER


We wanted to know if we can implement auto-scaling on the Access gateway Servers.

We are currently using the sps servers with Microsoft Azure Cloud.


Release : 12.6



We do not offer specific support for Azure and auto-scaling. Implementation is usually handled by services, not support. Siteminder does only cares about the operating system, not the hardware/appliance/cloud platform it is running on.

However, it should work. Depending on what you are doing there may be some issues that need to be taken into consideration. When the agents start up they connect to the policy server, have to download ACOs, have yet to start caching etc so the first few transactions on a newly spun up instance will always slower than already active agents for the first few seconds to minutes. This is heavily dependent on your implementation and support cannot really provide proper implementation advice on this. Personally - this is not Broadcom policy - I would suggest, if possible, keeping one (or more) more instance active than you require for the anticipated load which would give other instances more time to spin up, or somehow do load balancing so that newly spun up instances are not hit immediately after spinning up by a huge load.

In essence, siteminder is doing more than an apache instance. It is connecting to the policy server, which is then having potentially to read policy servers, user directories, read and write to session stores etc. This takes time until caching starts having an effect.

You would need a way of scripting smreghost to register the host you are spinning up.

See the following for an explanation of how the shared secret is generated: