PRPC 7 and cookie persistence timeout settings
Customer has load balancer issues with persistence timeout by ip address; looking at cookie persistence.
Looking for Pega engineer or product person confirmation:
1) is cookie persistence the preferred method of load balancing with Big IP with version 7.1?
2) Any setup issues to consider?
Message was edited by: Lochan to add Category
Pegasystems Inc.
US
yes, please see basic BigIP F5 load balancer setup in HA guide: https://pdn.pega.com/understanding-secu0008-alert-%E2%80%93-cross-site-forgery-attack-detected-and-blocked/understanding…
Pegasystems
US
Hi Kevin,
Thank you for the document. My customer went through the guide and here’s the response:
The HA doc describes a more complicated functionality than what we are wanting to employ.
Our goal is to employ cookie persistence from big IP where the big IP will send user back to the JVM it was at, provided the user logs back in within the persistence time setting we have set - at 30 minutes on big IP.
Currently, big IP has an IP persistence, but since we have heartbeats from the JVM to the IPs at all times, even when the IPs aren't online, the persistence is never expiring. Thus, users are always attached to their server until a JVM restart.
How do we design it so that the persistence expires?
Thanks.
Rich
Pegasystems Inc.
US
assuming you customer uses cookie persistence as recommended by Pega. You can use session cookie when creating persistence profile: SOL7168 - Configuring a session cookie persistence profile. I believe that is the default setting as well.
Us Bank
US
Hi, I work with Rich Jackson who originated this question. I just want to emphasize one part of this that will make us feel good about this question. It is: If we switch to cookie persistence, is there anything from the PRPC standpoint that we need to configure ? Do we need to set a prconfig or anything? I highly doubt it. I think we just configure it on the BIG IP side and we are good to go... We want to make sure.