PUBLIC - Liferay Portal Community Edition

When re-visiting a site that has been reset (e.g. database reset), cookies in the browser cause scary stack trace error on accessing site

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: No Longer Reproducible
  • Affects Version/s: 6.1.0 CE RC1
  • Fix Version/s: 6.1.X EE, 6.2.0 CE M3
  • Component/s: Authentication
  • Labels:
    None
  • Environment:
    Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 896ad0e9a6f1b1c5dfc7b2948e4757251b791d3e.
    Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 5e2298226107eed1d7d69457ac8b0aa6a9bb0a7d.
  • Fix Priority:
    3
  • Similar Issues:
    Show 4 results 

Description

I installed Liferay using built-in HSQLDB, and logged in (selecting "remember me").

Later on, I switched over to MySQL, and reset the database. When accessing the site using the existing browser, a scary stack trace error is shown (see attachment). Clearing cookies resolves this issue.

I would expect either a warning, or Liferay should simply act like the "remember me" cookies weren't set and allow me access as an unauthenticated user.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Sophia Zhang added a comment -

I was unable to reproduce it on trunk-87598.So I will close it.
BTW just to be sure,did you clean up cookies before you used HSQLDB?

Show
Sophia Zhang added a comment - I was unable to reproduce it on trunk-87598.So I will close it. BTW just to be sure,did you clean up cookies before you used HSQLDB?
Hide
Permalink
James Falkner added a comment -

This issue is still occuring in 6.1 GA2, as reported by a couple of community members. Of course, it works if you clear your browser cookies, but if you don't do that (and many people don't know how to do this), you still should not get a scary stack trace. It should just assume you are unauthenticated and do whatever it normally does in that case (e.g. redirect to login screen).

Show
James Falkner added a comment - This issue is still occuring in 6.1 GA2, as reported by a couple of community members. Of course, it works if you clear your browser cookies, but if you don't do that (and many people don't know how to do this), you still should not get a scary stack trace. It should just assume you are unauthenticated and do whatever it normally does in that case (e.g. redirect to login screen).
Hide
Permalink
Dave Kliczbor added a comment -

Can confirm this issue with a fresh GA2 bundle when trying to minimize the DB for project startup.

Steps to reproduce:

  • Get the bundle. Start it locally (for http://localhost:8080/), run the wizard, log in, etc.
  • See you don't like the welcome-theme for your project and want every trace of it out of the DB by repopulating it from scratch.
  • Shut down tomcat.
  • Delete directory contents of data/, tomcat/work, tomcat/temp
  • Do NOT delete portal-setup-wizard.properties
  • Delete unneccessary plugin directories: tomcat/webapps/resources-importer-web and tomcat/webapps/welcome-theme
  • Do NOT clear your browser cookies (anyway, why should I? If the cookie is not valid anymore, it should not do harm)
  • Start tomcat. Be greeted with a blank page (HTTP response size: 0 bytes).
  • View log: See the stacktrace mentioned in the original post.

This worked in GA1 – I got the login screen for the admin user set in portal-setup-wizard.properties/portal-ext.properties. I'd call it a regression bug.

Show
Dave Kliczbor added a comment - Can confirm this issue with a fresh GA2 bundle when trying to minimize the DB for project startup. Steps to reproduce: Get the bundle. Start it locally (for http://localhost:8080/ ), run the wizard, log in, etc. See you don't like the welcome-theme for your project and want every trace of it out of the DB by repopulating it from scratch. Shut down tomcat. Delete directory contents of data/, tomcat/work, tomcat/temp Do NOT delete portal-setup-wizard.properties Delete unneccessary plugin directories: tomcat/webapps/resources-importer-web and tomcat/webapps/welcome-theme Do NOT clear your browser cookies (anyway, why should I? If the cookie is not valid anymore, it should not do harm) Start tomcat. Be greeted with a blank page (HTTP response size: 0 bytes). View log: See the stacktrace mentioned in the original post. This worked in GA1 – I got the login screen for the admin user set in portal-setup-wizard.properties/portal-ext.properties. I'd call it a regression bug.
Hide
Permalink
James Falkner added a comment -

This is really easy to reproduce:

  • Clear all cookies from your browser (I am using Chrome 23.0.1271.64 on a Mac)
  • Download and unzip the GA2 Tomcat bundle from here: http://sourceforge.net/projects/lportal/files/Liferay%20Portal/6.1.1%20GA2/liferay-portal-tomcat-6.1.1-ce-ga2-20120731132656558.zip/download
  • Run it using startup.sh (or startup.bat) - it will start up then open your browser to the Basic Configuration Page. Click "Accept" and then agree to the ToU and then give a new password. At this point you should be logged in.
  • Stop Tomcat using shutdown.sh (or shutdown.bat).
  • Delete the data/ directory in its entirety (e.g. rm -rf data from the Liferay Home directory)
  • Restart Tomcat
  • It will re-initialize the HSQL database, then pop up your browser to localhost, at which point you should get the scary stack trace and an exception about "No such user".
Show
James Falkner added a comment - This is really easy to reproduce: Clear all cookies from your browser (I am using Chrome 23.0.1271.64 on a Mac) Download and unzip the GA2 Tomcat bundle from here: http://sourceforge.net/projects/lportal/files/Liferay%20Portal/6.1.1%20GA2/liferay-portal-tomcat-6.1.1-ce-ga2-20120731132656558.zip/download Run it using startup.sh (or startup.bat) - it will start up then open your browser to the Basic Configuration Page. Click "Accept" and then agree to the ToU and then give a new password. At this point you should be logged in. Stop Tomcat using shutdown.sh (or shutdown.bat). Delete the data/ directory in its entirety (e.g. rm -rf data from the Liferay Home directory) Restart Tomcat It will re-initialize the HSQL database, then pop up your browser to localhost, at which point you should get the scary stack trace and an exception about "No such user".
Hide
Permalink
Sophia Zhang added a comment - - edited

Hey James,

Thanks for your reply. Now it's very simple to reproduce this issue. Thank you.

Show
Sophia Zhang added a comment - - edited Hey James, Thanks for your reply. Now it's very simple to reproduce this issue. Thank you.
Hide
Permalink
Sophia Zhang added a comment -

Hi,

Although I can reproduce it on our released CE version 6.1.1-ce-ga2, I have to close it since now I am unable to reproduce it on our trunk head:
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 5e2298226107eed1d7d69457ac8b0aa6a9bb0a7d.
When re-initialize the HSQL database, portal requests user to login again, Accept Terms of Use, reset password and retype password reminder. Thanks.

Show
Sophia Zhang added a comment - Hi, Although I can reproduce it on our released CE version 6.1.1-ce-ga2, I have to close it since now I am unable to reproduce it on our trunk head: Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 5e2298226107eed1d7d69457ac8b0aa6a9bb0a7d. When re-initialize the HSQL database, portal requests user to login again, Accept Terms of Use, reset password and retype password reminder. Thanks.

People

Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
    Days since last comment:
    29 weeks, 1 day ago