WORKAROUND
Cookie based "Sticky sessions" are compulsory when using load balancers.
Other load balancing methods which do not use cookie insertion for "sticky sessions" or "session permanence" may create situations where the requests are redirected to different webservers depending on the load balancer configuration, which will create errors due to scripts not being loaded, or loaded in the incorrect order.
By default, Identity Manager Web Applications manage sessions with the in-process mode and use cookies to track the sessions. These cookies can be used by most load balancers on the market to track sessions accordingly, and include their own cookies to track sessions with more precision. More information can be found here: Session-State Modes.
For this cookie insertion to work, the https traffic has to be deciphered on the load balancer, either using "ssl offloading", or "ssl bridging", and in any case the session maintained on the load balancer has to follow the IIS provided session lifecycle.
STATUS
Enhancement Request #17722 has been submitted to improve Identity Manager documentation regarding the configuration of load balancers. This will be included in a future version of Identity Manager along with other improvements and listed in the release notes.
© 2025 One Identity LLC. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center