You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Ramesh Mani (JIRA)" <ji...@apache.org> on 2019/05/21 17:55:01 UTC
[jira] [Updated] (RANGER-2437) Update grant/revoke error message to
provide more information about the principal type
[ https://issues.apache.org/jira/browse/RANGER-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramesh Mani updated RANGER-2437:
--------------------------------
Attachment: 0001-RANGER-2437-Update-grant-revoke-error-message-to-pro.patch
> Update grant/revoke error message to provide more information about the principal type
> --------------------------------------------------------------------------------------
>
> Key: RANGER-2437
> URL: https://issues.apache.org/jira/browse/RANGER-2437
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Reporter: Fredy Wijaya
> Priority: Major
> Attachments: 0001-RANGER-2437-Update-grant-revoke-error-message-to-pro.patch
>
>
> In related to this: https://issues.apache.org/jira/browse/IMPALA-8551
> when granting/revoking to an invalid user/group, Ranger only throws a generic Exception which a generic error message, such as "HTTP: 400: foo is Not Found". This could happen when:
> - grantor is an invalid user
> - the target grant user is invalid
> - the target grant group is invalid.
> It would be nice if Ranger could either throw a specialized exception or update the error message to provide more information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)