ChinmayHegde24 opened a new pull request, #688: URL: https://github.com/apache/ranger/pull/688
Currently, when the handleEncryptedKeyOp() method in KMS.java is invoked via the API, there is no visibility into whether the request is performing a decryptKey or reEncryptKey operation as same path gets logged for both operations as it hits the same method. So after this patch opCode will be included in AccessLog pattern. e.g In access logs we can see opcode appended <ip> - - [<DateTime>] "GET /kms/v1/keys/names" 200 3 50 - <ip> - - [<DateTime>] "GET /kms/v1/key/key1/_eek" 500 288 29 generate <ip> - - [<DateTime>] "POST /kms/v1/keyversion/test-2@1/_eek" 400 176 16 reencrypt <ip> - - [<DateTime>] "POST /kms/v1/keyversion/test-2@1/_eek" 400 176 14 decrypt ## How was this patch tested? Checked Access logs after hitting endpoints through Docker setup Mvn local build -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
