Bug 1032107

Summary:	When using LDAP, when user logs out of web console they cannot log back in without closing browser
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Catherine Robson <crobson>
Component:	Domain Management	Assignee:	Darran Lofthouse <darran.lofthouse>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kremensky <pkremens>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.0.0	CC:	brian.stansberry, crobson, darran.lofthouse, emuckenh, hbraun
Target Milestone:	---	Flags:	crobson: needinfo-
Target Release:	EAP 6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-18 09:33: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 Catherine Robson 2013-11-19 15:00:21 UTC

Description of problem:  When LDAP was enabled, whenever the user logged out any logins failed until they closed the browser and restarted it again.


Version-Release number of selected component (if applicable):
6.2.0-CR1


How reproducible:
Have no reproduced on another system.  Saw this on a SA's system with LDAP enabled.  Needs reproducing.


Steps to Reproduce:
1. Enable LDAP user authentication
2. Log into web console
3. Log out of web console
4. Attempt to log back into web console --> FAILURE
5. Close browser & reopen
6. Attempt to log back into web console --> SUCCESS

Actual results:
User must close browser to log back in after logout.

Expected results:
Users should be able to log back in after logging on without closing browser.

Comment 1 Darran Lofthouse 2013-11-20 13:10:58 UTC

Pass my way if you want first Harald, we do have a change needed to the logout handler first for BASIC auth.

Comment 2 Harald Pehl 2013-11-20 13:58:33 UTC

I'm afraid we'll never get this right, until we implement https://issues.jboss.org/browse/HAL-96.

Comment 3 Darran Lofthouse 2013-11-20 14:08:16 UTC

Upstream now is probably a good time to be getting this in.

For EAP however that will be a bigger job due to being a different HTTP server.

Comment 4 Darran Lofthouse 2014-07-08 13:58:20 UTC

Is this still an issue with EAP 6.3?  We did revisit HTTP BASIC logout handling in EAP 6.3 so this may already be fixed.

Comment 5 Petr Kremensky 2014-07-18 09:33:55 UTC

This is no longer an issue in 6.3.0 (tested with EAP 6.3.0.ER10), thus closing.