You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Ankush Bangroo (JIRA)" <ji...@apache.org> on 2015/02/13 11:07:13 UTC

[jira] [Updated] (OAK-2516) Add user information in audit events in oak

     [ https://issues.apache.org/jira/browse/OAK-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ankush Bangroo updated OAK-2516:
--------------------------------
    Description: 
All operations in the repository are being logged by org.apache.jackrabbit.oak.jcr.operations logger, however the above logger does not include the user information triggering these operations.

Hence we do not have information on the user triggering the read and writes on the repository.

  was:
The AEM6.0 configuration for the audit.log is using “org.apache.jackrabbit.core.audit” as the logger.
This file is not present in Oak and hence nothing is being logged in the audit logs.
We have a customer who has a business requirement to track the users making changes to the osgi configurations.For this we want to know the correct logger which will track all the changes in the repository as was happening before[ CRx2.x]


        Summary: Add user information in audit events in oak  (was: Logging audit events in oak)

> Add user information in audit events in oak
> -------------------------------------------
>
>                 Key: OAK-2516
>                 URL: https://issues.apache.org/jira/browse/OAK-2516
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: oak-jcr
>    Affects Versions: 1.0.11
>            Reporter: Ankush Bangroo
>
> All operations in the repository are being logged by org.apache.jackrabbit.oak.jcr.operations logger, however the above logger does not include the user information triggering these operations.
> Hence we do not have information on the user triggering the read and writes on the repository.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)