[
https://issues.apache.org/jira/browse/RANGER-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18100617#comment-18100617
]
Ramachandran Krishnan commented on RANGER-5716:
-----------------------------------------------
Merged into ranger-2.9 branch commit
detail:[https://github.com/apache/ranger/commit/69315f3ff81138fe532a3a1abf9cd3f0ee90151d]
> KMS Ranger audit: wrong assertAccess overload puts key name in Client IP and
> leaves Resource empty
> --------------------------------------------------------------------------------------------------
>
> Key: RANGER-5716
> URL: https://issues.apache.org/jira/browse/RANGER-5716
> Project: Ranger
> Issue Type: Task
> Components: kms
> Affects Versions: 2.8.0
> Reporter: Ramachandran Krishnan
> Assignee: Ramachandran Krishnan
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Several KMS REST handlers call the wrong {{assertAccess}} overload in
> {{{}KMS.java{}}}. They pass the encryption key name where the code expects
> the client IP address. Ranger KMS plugin audits then show the key name (e.g.
> {{{}test_13_10{}}}) in the Client IP column and an empty Resource column.
> This is not a multi-threading or audit-handler race. It is a long-standing
> parameter wiring bug, most visible under concurrent load (e.g.
> {{{}ranger-tools/.../stress/stress_kms.py{}}}).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
