Configuring JSESSIONID path issue
SummaryThe requirement is to configure the cookie path at the application server level for JSESSIONID to be the context root of Pega application "/prweb".
The issue at hand is that a second application on the same server is establishing a new JSESSIONID and when control returns to Pega, it does not recognize and forces user to log back in.
Error MessagesNot applicable.
Steps to ReproduceIn this scenario,user had an environment where static content was served up by a second application.
Root CauseIf the second application encounters a HTTP 500 error in its process, it re-establishes a new session. If not, Pega will resume normally as the JSESSIONID is unchanged.
In WebSphere, the solution is best achieved by configuring the JSESSIONID to have a path of "context-root". Therefore, Pega's session will operate with JSSESIONID path of /prweb and influences from other applications will not effect it.
Published August 24, 2016 - Updated August 31, 2016