Bug 1013056

Summary: RBAC: Enhanced behavior from read-operation-names and read-operation-description results
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Brian Stansberry <brian.stansberry>
Component: Domain ManagementAssignee: Kabir Khan <kkhan>
Status: CLOSED CURRENTRELEASE QA Contact: Ladislav Thon <lthon>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.0CC: emuckenh, kkhan
Target Milestone: ER6   
Target Release: EAP 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-15 16:55:35 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.