ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitin Galave (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RANGER-1890) The permission of "Kafka Admin" can not support "Select/Deselect All" when add/edit Kafka policy
Date Wed, 22 Nov 2017 14:20:00 GMT

    [ https://issues.apache.org/jira/browse/RANGER-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262582#comment-16262582
] 

Nitin Galave commented on RANGER-1890:
--------------------------------------

[~zhangqiang2] All component definition has attribute call _impliedGrants_ in _accessType_
property. If user select permission and that permission has '_impliedGrants_' for other permissions
then user has privileges of all those permissions.This is aumatically handle at the backend.
*For example*: 
In KAFKA service definition contains permission : '_Kafka admin_' and it has _impliedGrants_
property : ["publish", "consume", "configure", "describe", "create", "delete"] ,So its mean
user has all this privileges.

And for publish permission has _impliedGrant_ as [describe].
So whenever user select publish, So its mean user has publish and describe permission.

All these scenarios are already handled at the backend. So we do not need to handle it on
UI.
If we handle all these cases it on UI this might confuse the end user.

cc: [~vperiasamy]

> The permission of "Kafka Admin" can not support "Select/Deselect All"  when add/edit
Kafka policy
> -------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-1890
>                 URL: https://issues.apache.org/jira/browse/RANGER-1890
>             Project: Ranger
>          Issue Type: Bug
>          Components: admin, Ranger
>            Reporter: Qiang Zhang
>            Assignee: Qiang Zhang
>            Priority: Minor
>         Attachments: 0001-RANGER-1890-The-permission-of-Kafka-Admin-can-not-su.patch
>
>
> The current logic is as following:
> 1. Other checkbox will not be selected when the "Kafka Admin" was selected.
> 2. Other checkbox will not be deselected when the "Kafka Admin“ checkbox" was deselected.
> The right logic should be as following:
> 1. Other checkbox will be selected when the "Kafka Admin" was selected.
> 2. Other checkbox will be deselected when the "Kafka Admin" was deselected.
> 3. When all Other checkboxes are selected, cancel one of them, the "Kafka Admin" checkbox
will be canceled.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message