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

Madhan Neethiraj updated RANGER-5814:
-------------------------------------
    Description: 
Condition expressions in policies can refer to various attributes available in 
the request context, such as:
 - {{{}clientType{}}}: the type of the client that accesed the resource
 - {{{}clusterType{}}}: the type of the cluster in which the service is 
deployed in - onprem, cloud, cleanroom
 - {{{}clusterName{}}}: the name of the cluster in which the service is 
deployed in - prod, test, analyst, etc

These attributes can be referenced policies, as shown below, to grant/deny 
accesses on specific criteria:
 - {{REQ.clusterName == 'etl'}}
 - {{REQ.clientType == 'cli'}}

Application type, that represents the type of the application/service that 
serves the accessed resource (for example: HiveServer2, Impala, Trino) should 
be made available in the request context - so that policies can be setup to 
grant/deny accesses based on the application type, using expressions such as:
 - {{REQ.appType == 'hiveMetastore' || REQ.appType == 'impala'}}

  was:
Condition expressions in policies can refer to various attributes available in 
the request context, such as:

- {{clientType}}: the type of the client that accesed the resource
- {{clusterType}}: the type of the cluster in which the service is deployed in 
- onprem, cloud, cleanroom
- {{clusterName}}: the name of the cluster in which the service is deployed in 
- prod, test, analyst, etc

These attributes can be referenced policies, as shown below, to grant/deny 
accesses on specific criteria:
- {{REQ.clusterName == 'etl'}}
- {{REQ.clientType == 'cli'}}

Application type, that represents the type of the application/service that 
serves the accessed resource (for example: HiveServer2, Impala, Trino) should 
be made available in the request context - so that policies can be setup to 
grant/deny accesses based on the application type.


> application-type should be made available in policy conditions
> --------------------------------------------------------------
>
>                 Key: RANGER-5814
>                 URL: https://issues.apache.org/jira/browse/RANGER-5814
>             Project: Ranger
>          Issue Type: Improvement
>          Components: plugins
>            Reporter: Madhan Neethiraj
>            Assignee: Madhan Neethiraj
>            Priority: Major
>
> Condition expressions in policies can refer to various attributes available 
> in the request context, such as:
>  - {{{}clientType{}}}: the type of the client that accesed the resource
>  - {{{}clusterType{}}}: the type of the cluster in which the service is 
> deployed in - onprem, cloud, cleanroom
>  - {{{}clusterName{}}}: the name of the cluster in which the service is 
> deployed in - prod, test, analyst, etc
> These attributes can be referenced policies, as shown below, to grant/deny 
> accesses on specific criteria:
>  - {{REQ.clusterName == 'etl'}}
>  - {{REQ.clientType == 'cli'}}
> Application type, that represents the type of the application/service that 
> serves the accessed resource (for example: HiveServer2, Impala, Trino) should 
> be made available in the request context - so that policies can be setup to 
> grant/deny accesses based on the application type, using expressions such as:
>  - {{REQ.appType == 'hiveMetastore' || REQ.appType == 'impala'}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to