Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1027586 - RBAC: Web console is too coarse-grained with application resources
RBAC: Web console is too coarse-grained with application resources
Status: NEW
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity high
: ---
: EAP 6.4.0
Assigned To: Heiko Braun
Pavel Jelinek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-07 02:11 EST by Ladislav Thon
Modified: 2018-03-06 15:36 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Known Issue
Doc Text:
In this release of JBoss EAP 6, when a resource is defined as an application resource, the console may not reflect that definition. This is because the console often groups several resources under one view. The controls in the views are available if all related resources are writable. If any of these resources is configured as an application resource, however, the related controls will still be disabled. The current workaround is to, if possible, configure all resource types associated with a subsystem as application resources.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Enhancement
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker HAL-300 Major Resolved Mismatch between application resources and access control configuration 2018-10-22 10:38 EDT

  None (edit)
Description Ladislav Thon 2013-11-07 02:11:55 EST
As we found in bug 1017786, the console is too coarse-grained with application resources. E.g., if one makes "data-source" application resource, the web console doesn't allow editing datasources unless also "xa-data-source" is made application resource. This is a usable workaround for datasources, but there is no such usable workaround e.g. for JMS.
Comment 4 Scott Mumford 2013-12-01 21:15:08 EST
Modified Doc Text content and marked for inclusion in the 6.2 Release Notes document.
Comment 5 Jakub Cechacek 2014-07-16 07:19:46 EDT
Moving to 6.4 as the issue is still valid for 6.3
Comment 6 JBoss JIRA Server 2015-07-20 02:32:37 EDT
Heiko Braun <ike.braun@googlemail.com> updated the status of jira HAL-300 to Resolved

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