Legacy Knowledge Base
Published Jun. 30, 2025

Blank screen is seen after password reset

Written By

Dia Seung

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

  • A blank screen (with url http://localhost:8080/c) is seen after user password is reset.
  • The expected behavior after password reset is for users to A) be successfully redirected to Liferay home page and B) remain logged in.
    • However, in DXP 7.4 u50 (and below) with session.enable.phishing.protection=false set in portal-ext.properties, users are instead redirected to a blank page after password reset.
    • In DXP 7.4 u51 and higher with session.enable.phishing.protection=false , users are successfully rerouted to the Liferay home page, but users are logged out. 

Environment

  • DXP 7.4

Resolution

  • When session.enable.phishing.protection property is set to false in portal-ext.properties in DXP 7.4, sessions are being invalidated in PasswordModifiedFilter due to differences in passwordModifiedDate and creation date of the current session.  This is a bug solved by LPS-182143 -- please update to a more recent Update release with the fix included or reach out to Support for a hotfix including the fix. 
  • A valid workaround would be to set session.enable.phishing.protection=true instead in portal-ext.properties.

Additional Information

 

Did this article resolve your issue ?

Legacy Knowledge Base