> On Sept. 16, 2020, 3:44 p.m., Ramesh Mani wrote:
> > kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSMDCFilter.java
> > Lines 77 (patched)
> > <https://reviews.apache.org/r/72847/diff/1/?file=2239325#file2239325line78>
> >
> >     do we need to check only the "/kms/api/status" path here and rest go 
> > through the regular flow?

Yes. APIs such as "/kms/v1/" are written in KMS.java require authentication and 
authorization.


- Dhaval


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72847/#review221875
-----------------------------------------------------------


On Sept. 16, 2020, 6:31 p.m., Dhaval Shah wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72847/
> -----------------------------------------------------------
> 
> (Updated Sept. 16, 2020, 6:31 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Dineshkumar Yadav, Jayendra Parab, 
> Kishor Gollapalliwar, Abhay Kulkarni, Mehul Parikh, Pradeep Agrawal, Ramesh 
> Mani, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2998
>     https://issues.apache.org/jira/browse/RANGER-2998
> 
> 
> Repository: ranger
> 
> 
> Description
> -------
> 
> Need to construct the API which can be accessible without user credentials 
> for Ranger KMS service status. So when service Ranger KMS is successfully 
> started there should be status saying "Ranger KMS is up and running" when we 
> hit particular API.
> 
> 
> Diffs
> -----
> 
>   
> kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSAuthenticationFilter.java
>  944b3d483 
>   kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSMDCFilter.java 
> da8f71599 
>   
> kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/RangerKMSRestApi.java
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/72847/diff/1/
> 
> 
> Testing
> -------
> 
> Successfully tested the status API.
> 
> 
> Thanks,
> 
> Dhaval Shah
> 
>

Reply via email to