Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Pega session/cookie manage

SA-43078

Summary



User is running Pega 7.1.8 and want to apply the HA for their service. The topology as below:

User >https:443>Netscaler-LB >http:9080>WASND-Node01 + WASND-Node02

By following some document (How to configure a reverse proxy server), user already setup HTTP Header (at LB Level) : PegaRULES-SetContextURI. ContextRewriteEnabled to true in prconfig.xml.

User verified in Pega Clipboard and pxReqContextURI is the same as PegaRULES-SetContextURI.
When trying to test (shutdown 1 node), the Pega still asking for login again.

Error Messages



Not Applicable


Steps to Reproduce



1. Configure two nodes on Elastic Load Balancer (ELB).
2. Login with one user landing on one of the node.
3. Bring down the node or node gets crashed.User gets routed to another node.


Root Cause



Due to security reasons user must re-authenticate on server crash and this use-case is only supported with SSO enabled application environments(see below). Refer to crash recovery section in Pega 7.1.8 HA Guide for more details.

All high availability settings for crash recovery are defined per cluster. Use single sign-on (SSO) to avoid re-authentication.




Resolution



Here’s the explanation for the reported behavior:

With the current setup, From a client machine when a User X is logged in Pega application and is landed to node A through load balancer.

1. One HTTP session is established and Pega RequestorID is created on node A.
2. If node A goes down/crashes – The load balancer will route the subsequent requests from node A to the other nodes having less traffic.
3. During this process, the User X requestor session info is not maintained at node B or C.
4. As the node B or C is unaware of User X session state, so it will be prompted for authentication at application level to serve further requests.

The HA features restore the requestors clipboard pages/state on the other node on re-authentication but this will not perform session replication to skip the authentication part during node crash.

Due to security reasons user must re-authenticate on server crash and this use-case is only supported with SSO enabled application environments. Refer to crash recovery section in Pega 7.1.8 HA Guide for more details.

Suggest Edit

Published December 15, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us