Bug 1007016

Summary: URL contains message parameter 'invalid username or password' after successful login
Product: [Retired] JBoss BPMS Platform 6 Reporter: Radovan Synek <rsynek>
Component: Business CentralAssignee: Maciej Swiderski <mswiders>
Status: CLOSED CURRENTRELEASE QA Contact: Radovan Synek <rsynek>
Severity: low Docs Contact:
Priority: low    
Version: 6.0.0CC: etirelli, lpetrovi
Target Milestone: ER1   
Target Release: 6.0.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:02:55 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 Radovan Synek 2013-09-11 18:05:08 UTC
Try to log in to business-central with wrong password. Login screen reappears and there is following parameter in URL:
message=Login failed: Invalid UserName or Password

Now, log in successfully and check the URL - it still contains this parameter.

expected result: this parameter shouldn't be in URL after successful login.

version: BRMS-6.0.0.ER2

Comment 4 Maciej Swiderski 2014-02-03 17:52:44 UTC
fixed, no message is visible in the URL. note that in case user is not authorized (but was successfully authenticated) user will be presented with error message and button to try to logon with another user. Difference is that we do not display logon form directly as 403 error page (not authorized) is not part of the logon procedure and thus requires redirect.

kie-wb-distributions:
master:
https://github.com/droolsjbpm/kie-wb-distributions/commit/5f27218acb9aa83d3b8f39a63681359cc7d9c0cc

6.0.x:
https://github.com/droolsjbpm/kie-wb-distributions/commit/bc27b34f41c082ccba67e3bddb5a82bb2f398c11

Comment 5 Lukáš Petrovický 2014-02-07 16:19:51 UTC
This no longer has a target release of 6.0.0.

Comment 6 Radovan Synek 2014-02-20 11:12:05 UTC
Verified with BPMS-6.0.1.ER1

Comment 7 Radovan Synek 2014-03-18 14:25:47 UTC
qe_test_coverage: does not have any impact on functionality.