Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1026823 - Provide a reliable way to clear "ROLE" headers set by "Run as" dialog
Provide a reliable way to clear "ROLE" headers set by "Run as" dialog
Status: VERIFIED
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity medium
: ER1
: EAP 6.4.0
Assigned To: Harald Pehl
Pavel Jelinek
:
Depends On:
Blocks: 1176535
  Show dependency treegraph
 
Reported: 2013-11-05 08:51 EST by Jakub Cechacek
Modified: 2018-03-06 15:36 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In previous releases of JBoss EAP 6, it was found that when a SuperUser acted on behalf of another user (with the *Run As...* link), their role was not reset after the action was taken. This issue has been addressed and users no longer need to close the browser window and re-access the Web Console for roles to be reset.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jakub Cechacek 2013-11-05 08:51:18 EST
Currently the only reliable way to clean ROLE headers is logout. In standalone this can be achieved by using "no preselection" option in "Run as" dialog, however this doesn't work in domain mode. 

This behavior is confusing for customer and has to be properly document unless we managed to fix this until GA is released.
Comment 1 Scott Mumford 2013-12-01 21:09:07 EST
Modified Doc Text content and marked for inclusion in the 6.2 Release Notes document.
Comment 2 Jakub Cechacek 2014-07-16 07:18:16 EDT
Moving to 6.4 as the issue is still valid for 6.3
Comment 5 Pavel Jelinek 2015-01-21 09:08:08 EST
Verified for EAP 6.4.0.ER1

Note You need to log in before you can comment on or make changes to this bug.