You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jeff Sposetti (JIRA)" <ji...@apache.org> on 2015/05/23 00:00:17 UTC

[jira] [Updated] (AMBARI-11350) Finer-grained role AuthZ for Ambari Users

     [ https://issues.apache.org/jira/browse/AMBARI-11350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Sposetti updated AMBARI-11350:
-----------------------------------
    Summary: Finer-grained role AuthZ for Ambari Users  (was: Ambari finer-grain authorization)

> Finer-grained role AuthZ for Ambari Users
> -----------------------------------------
>
>                 Key: AMBARI-11350
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11350
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jeff Sposetti
>
> Ambari to provider role-based access controls beyond today's Ambari Admin, Operator and Read-Only permissions.
> || Role || Description ||
> | Read-only | This exists as of Ambari 2.0. Read-only view of cluster information, including configurations, service status and health alerts|
> | *Service Administrator* | Provides control of service lifecycle (start/stop/restart/decomm/recom) |
> | *Service Operator* | Service Admin + ability to re-configure (change/compare/revert), configure HA |
> | *Cluster Operator* | Service Operator + enable/disable kerberos, modify alerts, add service, perform upgrade |
> | Operator | This exists as of Ambari 2.0. Full cluster control.|
> | Ambari Admin | This exists as of Ambari 2.0. Full cluster control + manage user, groups and views and this flag is applicable to any user regardless of Role |



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)