legacy-knowledge-base
Publicado Jul. 25, 2002

JSESSIONID Changes as Part of Liferay Security

written-by

Justin Choi

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

legacy-article

learn-legacy-article-disclaimer-text

This article documents Liferay's position regarding the Session Identifier (JSESSIONID), including how and why a new JSESSIONID is generated. 

Resolution

Customers doing their own security scan of the Liferay platform might have noticed that a new JSESSIONID may have been generated. This might even be flagged as a security risk, but actually, it is not.  The reason why the Session Identifier changes is because it is part of the overall security mechanism.

By default, the generated JSESSIONID can change whenever a user logs in to the Liferay platform, because, as a security measure, the platform attempts to invalidate the previous session. In Liferay platforms, the portal property session.enable.phishing.protection is set to true by default, unless explicitly changed in the portal-ext.properties file. Other application servers may use a call, such as request.getSession(true);, to achieve the same results.

This feature is just one part of the many security measures that Liferay engineers have put in place to protect the platform against threats. 

did-this-article-resolve-your-issue

legacy-knowledge-base