Bug 1013056 - RBAC: Enhanced behavior from read-operation-names and read-operation-description results
Summary: RBAC: Enhanced behavior from read-operation-names and read-operation-descript...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER6
: EAP 6.2.0
Assignee: Kabir Khan
QA Contact: Ladislav Thon
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-27 17:34 UTC by Brian Stansberry
Modified: 2013-12-15 16:55 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:55:35 UTC
Type: Enhancement
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-1756 0 Major Resolved Add access-control parameter to read-operation-description operation 2015-07-03 06:37:07 UTC
Red Hat Issue Tracker WFLY-2131 0 Major Resolved read-operation-names to return a filtered list of allowed operations 2015-07-03 06:37:07 UTC

Description Brian Stansberry 2013-09-27 17:34:45 UTC
This is an RFE issue to consider backporting some minor RBAC-related features from WF to EAP.

For WF 8 we are adding two minor improvements to the management API description operations:

1) Ability to add an "access-control" parameter to the "read-operation-names" operation and if true (default is false) have the response exclude operations the user is not authorized to execute.

2) Ability to add an "access-control" parameter to the "read-operation-description" operation and if true (default is false) have the response include descriptive data re: the user's ability to execute the operation.


The much more commonly used read-resource-description operation already provides this information, which is why this is a minor feature we didn't target for 6.2.

Comment 6 Ladislav Thon 2013-10-21 09:53:57 UTC
Verified with EAP 6.2.0.ER6.


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