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

Vikas Kumar updated RANGER-5649:
--------------------------------
    Description: 
KMS metric collection API should not require authentication. 

API:

 /kms/metrics/json

/kms/metrics/prometheus

 

{*}Reason{*}: Generally this API gets polled by some external tool at some 
defined interval. With authentication, in Kerberos enabled env (usually the 
case) it will create lot of load on KDC. This is not required.

 

*Update:*

Completely removing authentication is risk, instead considering to integrate 
external tools using DelegationToken approach. 

  was:
KMS metric collection API should not require authentication. 

API:

 /kms/metrics/json

/kms/metrics/prometheus

 

{*}Reason{*}: Generally this API gets polled by some external tool at some 
defined interval. With authentication, in Kerberos enabled env (usually the 
case) it will create lot of load on KDC. This is not required.


> [KMS]: Metric collection API should not require authentication
> --------------------------------------------------------------
>
>                 Key: RANGER-5649
>                 URL: https://issues.apache.org/jira/browse/RANGER-5649
>             Project: Ranger
>          Issue Type: Improvement
>          Components: kms
>            Reporter: Vikas Kumar
>            Assignee: Vikas Kumar
>            Priority: Major
>
> KMS metric collection API should not require authentication. 
> API:
>  /kms/metrics/json
> /kms/metrics/prometheus
>  
> {*}Reason{*}: Generally this API gets polled by some external tool at some 
> defined interval. With authentication, in Kerberos enabled env (usually the 
> case) it will create lot of load on KDC. This is not required.
>  
> *Update:*
> Completely removing authentication is risk, instead considering to integrate 
> external tools using DelegationToken approach. 



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

Reply via email to