Disabling the Crowd Audit Log

Still need help?

The Atlassian Community is here for you.

Ask the community


Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Crowd 3.2 introduced the Audit Log, which is a list of changes made to users in your directories either by other users/admins, or during synchronizations.  For various reasons, some people may not want this functionality enabled, and want to disable it.  

Resolution

There are 2 different options you have for disabling the audit log.

Disabling The Audit Log Only For Synchonizations

Perhaps you still want to use the audit log to track any changes to users made by other users, but not for changes made during a sync from a remote directory?  This is possible by adding the following JVM parameter to your <CROWD_INSTALL>/apache-tomcat/bin/setenv.sh (or setenv.bat for Windows) file:

-Dcrowd.audit.synchronisation.log.disable=true

Manual changes made in Crowd will still show up in the Audit log, but changes made during syncs from remote directories will be ignored.

Disabling the Audit Log Fully

This will completely disable the audit log.  The page to view the log will still be present in Crowd, but no updates will be written to the logs once this parameter is added.  Add the following JVM parameter  to your <CROWD_INSTALL>/apache-tomcat/bin/setenv.sh (or setenv.bat for Windows) file:

-Dcrowd.audit.log.disable=true


(warning) You will need to re-start Crowd for the above changes to take effect.




Last modified on Jan 2, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.