[
https://issues.apache.org/jira/browse/AMBARI-13814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-13814:
----------------------------------
Description:
Add (descriptive) label to permission resource and database schema to avoid
having to hardcode a descriptive name for a permission. For example:
||Permission Name||Permission Label||
|VIEW.USER|View User|
|CLUSTER.USER|Cluster User|
|SERVICE.OPERATOR|Service Operator|
|SERVICE.ADMINISTRATOR|Service Administrator|
|CLUSTER.OPERATOR|Cluster Operator|
|CLUSTER.ADMINISTRATOR|Cluster Administrator|
This descriptive label can be used in user interfaces so that a descriptive (or
friendly) name does not have to be hardcoded.
{noformat:title=API Call Example}
GET api/v1/permissions/1
200 OK
{
"href" : "http://your.ambari.server/api/v1/permissions/1";,
"PermissionInfo" : {
"permission_id" : 1,
"permission_name" : "AMBARI.ADMIN",
"permission_label" : "Administrator",
"resource_name" : "AMBARI"
}
}
{noformat}
was:
Add (descriptive) label to permission resource and database schema to avoid
having to hardcode a descriptive name for a permission. For example:
||Permission Name||Permission Label||
|VIEW.USER|View User|
|CLUSTER.USER|Cluster User|
|SERVICE.OPERATOR|Service Operator|
|SERVICE.ADMINISTRATOR|Service Administrator|
|CLUSTER.OPERATOR|Cluster Operator|
|CLUSTER.ADMINISTRATOR|Cluster Administrator|
This descriptive label can be used in user interfaces so that a descriptive (or
friendly) name does not have to be hardcoded.
> Add (descriptive) label to permission resource and database schema
> ------------------------------------------------------------------
>
> Key: AMBARI-13814
> URL: https://issues.apache.org/jira/browse/AMBARI-13814
> Project: Ambari
> Issue Type: Task
> Components: ambari-server, ambari-web
> Affects Versions: 2.2.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Labels: rbac
> Fix For: 2.2.0
>
> Attachments: AMBARI-13814_trunk_01.patch,
> AMBARI-13814_trunk_02.patch, AMBARI-13814_trunk_03.patch
>
>
> Add (descriptive) label to permission resource and database schema to avoid
> having to hardcode a descriptive name for a permission. For example:
> ||Permission Name||Permission Label||
> |VIEW.USER|View User|
> |CLUSTER.USER|Cluster User|
> |SERVICE.OPERATOR|Service Operator|
> |SERVICE.ADMINISTRATOR|Service Administrator|
> |CLUSTER.OPERATOR|Cluster Operator|
> |CLUSTER.ADMINISTRATOR|Cluster Administrator|
> This descriptive label can be used in user interfaces so that a descriptive
> (or friendly) name does not have to be hardcoded.
> {noformat:title=API Call Example}
> GET api/v1/permissions/1
> 200 OK
> {
> "href" : "http://your.ambari.server/api/v1/permissions/1";,
> "PermissionInfo" : {
> "permission_id" : 1,
> "permission_name" : "AMBARI.ADMIN",
> "permission_label" : "Administrator",
> "resource_name" : "AMBARI"
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
