Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Does Liferay DXP validate Session Identifiers?

Written By

Marcos da Silva Xavier

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

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Does Liferay DXP validate Session Identifiers? And yes, Liferay does validate Session Identifiers!

Environment

  • Liferay DXP

Resolution

  • As for the session configuration in the portal we have the https://github.com/liferay/liferay-portal/blob/master/portal-impl/src/system.properties#L567-L576 and the https://github.com/liferay/liferay-portal/blob/master/portal-impl/src/portal.properties#L2957-L3232 sections in our properties files with which the behavior of the session handling can be influenced.

    Nevertheless, the session validation/invalidation is always done by the underlying framework, by the servlet container (SC) / application server (AS) (for example Tomcat) which implements the respective Java API. So, the portal only passes the necessary parameters to make that work.

    The session is created and managed by the SC / AS, however, the portal puts some additional data there. For example when a user is being authenticated successfully. The portal triggers the invalidation of the session at some point, but also calls the appropriate Servlet API methods.

    While the portal as a web application is responding to requests, it may change the state of the session through parameters, attributes, cookies, it is always doing that through that servlet API.

Additional Information

 

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?