+++ This bug was initially created as a clone of Bug #1302034 +++ Description of problem: It's possible to remove inhertied permissions from Everyone's group. If for example user will inherit UserTemplateBasedVm role on Blank template. Then if he check in webadmin this inhertited permission, he can't remove it, but if he try to remove this inherited permission via REST it's removed successfully and also removed from Everyone's group. Version-Release number of selected component (if applicable): 3.6.3 How reproducible: always Steps to Reproduce: 1. Add external user to system. 2. Remove some of the inhertied permissions from Everyone group from user $ curl -X DELETE -H "Content-type: application/xml" -k -u admin@internal:password $URL/users/1905239d-0c8a-48bb-b454-f24915a128f7/permissions/00000004-0004-0004-0004-000000000355 Actual results: It's successfully deleted. Also from Everyone group Expected results: Inherited permissions from group shouldn't be possible to remove. Or could be, but don't remove it from group as well. Additional info: --- Additional comment from Juan Hernández on 2016-01-26 10:54:23 EST --- The API doesn't perform this kind of check, it just forwards the request from the caller to the backend. If deleting these permissions shouldn't be allowed then the backend should reject the operation and respond to the API with the appropriate error message.
Retargeting to 3.6.8 as we missed today's last normal 3.6.7 build
Verified with: rhevm-4.0.0.5-0.1.el7ev.noarch # curl -X DELETE -H "Content-type: application/xml" -k -u admin@internal:pass $URL/users/e18a0c55-567f-4419-a6df-1c03c944b3e7/permissions/00000017-0017-0017-0017-000000000229 <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <fault> <detail>[Cannot remove inherited permission]</detail> <reason>Operation Failed</reason> </fault>
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-1507.html