[
https://issues.apache.org/jira/browse/HADOOP-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843941#action_12843941
]
Amar Kamat commented on HADOOP-6586:
------------------------------------
Boris,
- If we want to model it as audit log, then should keep the naming consistent
with hdfs i.e classname.audit?
- I am working on MAPREDUCE-1543 and I have proposed a mapreduce friendly audit
log format. Surely we dont want 2 audit-log formats. Here is my
[proposal|https://issues.apache.org/jira/browse/MAPREDUCE-1543?focusedCommentId=12843936&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12843936].
Lets discuss it out. If the commons audit-log format turns out to be different
from mapreduce, then there should be some way to distinguish them.
> Log authentication and authorization failures and successes
> -----------------------------------------------------------
>
> Key: HADOOP-6586
> URL: https://issues.apache.org/jira/browse/HADOOP-6586
> Project: Hadoop Common
> Issue Type: New Feature
> Components: security
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Fix For: 0.22.0
>
> Attachments: HADOOP-6586-3.patch, HADOOP-6586-4.patch,
> HADOOP-6586-5.patch, HADOOP-6586-7.patch, HADOOP-6586-8-BP20-1.patch,
> HADOOP-6586-8-BP20.patch, HADOOP-6586-8.patch, HADOOP-6586.patch
>
>
> This jira will cover RPC authentication and SL authorizations logging.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
