You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by Kevin Minder <ke...@hortonworks.com> on 2013/10/02 22:07:01 UTC
Re: [jira] [Updated] (KNOX-23) Generate audit log of all gateway
activity
How do you feel about using this for the auditing to a database?
http://www.tutorialspoint.com/log4j/log4j_logging_database.htm
This little bit of config is the issue.
# Set database user name and password
log4j.appender.DB.user=user_name
log4j.appender.DB.password=password
On 9/26/13 4:02 PM, Kevin Minder (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/KNOX-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Kevin Minder updated KNOX-23:
> -----------------------------
>
> Fix Version/s: 0.4.0
>
>> Generate audit log of all gateway activity
>> ------------------------------------------
>>
>> Key: KNOX-23
>> URL: https://issues.apache.org/jira/browse/KNOX-23
>> Project: Apache Knox
>> Issue Type: New Feature
>> Components: Server
>> Affects Versions: 0.2.0
>> Reporter: Kevin Minder
>> Assignee: Vladimir Tkhir
>> Fix For: 0.4.0
>>
>>
>> From BUG-4302
>> All interactions that pass through the gateway should be recorded in a separate audit log. This should include the IP and principal of the caller and potentially some service specific information (e.g. HDFS file name)
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.