Rename cookie Pega-RULES
We have multiple Pega instances for different applications.
e.g http://localhost:8080/app1 & http://localhost:8080/app2
When user access /app1, the default cookie will be Pega-RULES domain:locahost
When user access /app2, the default cookie will be Pega-RULES domain:locahost
Due to the cookie name, both apps are having same cookie name. How can change the default Pega-RULES cookie name?
Thanks
Pegasystems Inc.
US
You can't change the Pega-RULES cookie name. We always add the context root to the cookie path so this separates the values so they wont cause issues. You can change the context root of /prweb, like in your example URLS, at deployment time.
Example:
Set-Cookie: Pega-RULES=<value>; Version=1; Comment="PegaRULES session tracking"; Path=/psupp
We do get support requests for applications sharing the same domain with different context roots with regards to load balancing, PRPC and other applications hosted in same domain. This ends up being an issue with the JSESSIONID that is typically used for session affinity. By default in some application servers they do not append the path to the cookie. Modification to include path or rename JSESSIONID cookie are done at application server level and this always resolves these types of issues.
Hope this helps.
--Chris
Updated: 25 May 2018 15:33 EDT
Pegasystems Inc.
US
To further touch on what Chris is talking about:
What you're looking to do is to change the JSESSIONID cookies to JSESSIONID_App1 and JSESSIONID_App2. Also, set the path on each to the context root (E.g. "/prweb"). This is the best practice approach to having multiple applications running through a single server and keeping their sessions from colliding...
See this - https://pdn.pega.com/support-articles/issue-while-accessing-two-pega-sso-environments