Bug 794035 (JBEPP-1104)

Summary: 404 Page on Failed Login attemp followed by correct login
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: Matt Wringe <mwringe>
Component: unspecifiedAssignee: Matt Wringe <mwringe>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.2.0.DEV03CC: mcupak, mwringe, theute
Target Milestone: ---   
Target Release: 5.2.0.ER03   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-1104
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-10 06:23:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matt Wringe 2011-08-22 18:10:50 UTC 
project_key: JBEPP

Steps to Reproduce:
1) click on 'sign in' link in top right corner of portal
2) enter the wrong password. This will redirect you to the login page
3) enter the wrong password again on the login page
4) enter the right password on the login page. You will be redirected to http://localhost:8080/portal/j_security_check?j_username=root which results in a 404 error
5) if you enter the portal url, you will be logged into the portal

Note: you need to enter the incorrect password twice. If you only enter the incorrect password in the popup and enter the correct password on the login page, then it will work as expected.
Comment 1 Matt Wringe 2011-08-22 18:27:31 UTC 
Link: Added: This issue depends GTNPORTAL-2039
Comment 2 Thomas Heute 2011-08-29 15:38:58 UTC 
indeed, initialURI value is wrong on second call
Comment 3 Matt Wringe 2011-08-29 15:54:27 UTC 
The linked issue has a patch which fixes the issue, but I am a bit confused over what the portalContext.getInitialURL is really suppose to do. The method doesn't make a lot of sense.
Comment 4 Thomas Heute 2011-10-03 21:08:39 UTC 
Release Notes Docs Status: Added: Not Required
Comment 5 Miroslav Cupák 2011-10-07 22:21:22 UTC 
Reopening. This is marked as fixed by 5.2.0.ER02, but it's still an issue there. It looks like the fix just didn't make it in time for ER02, I'll verify with ER03 when it's ready.