[
https://issues.apache.org/jira/browse/RANGER-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17448924#comment-17448924
]
Pradeep Agrawal commented on RANGER-3135:
-----------------------------------------
revert commit :
https://github.com/apache/ranger/commit/5d1272335156dfc6d32862c6ee9af2e92b087169
> Ranger always ponit out "User does not have permission for this operation"
> when user try to query a none-exist role
> -------------------------------------------------------------------------------------------------------------------
>
> Key: RANGER-3135
> URL: https://issues.apache.org/jira/browse/RANGER-3135
> Project: Ranger
> Issue Type: Improvement
> Components: admin
> Affects Versions: 2.0.0, 2.1.0
> Reporter: rujia
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: 0001-optimze-log-print-for-querying-roles.patch
>
>
> when i access /role/name/{name}, a Exception "User does not have permission
> for this operation" always been taken, even if this role doesn't exist .
> it is better to prompt user this role is not exist in this case when
> execute-user has admin permission.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
