You are here

Enabling auditing

This topic describes the auditing properties and how to enable auditing using these properties.
The different auditing properties are:
  • audit.enabled=true
  • audit.tagging.enabled=true
  • audit.alfresco-access.enabled=false
  • audit.alfresco-access.sub-actions.enabled=false
  • audit.cmischangelog.enabled=false
  • audit.dod5015.enabled=false
Note: It is recommended that you do not change the audit.enabled=true, audit.tagging.enabled=true and audit.dod5015.enabled=false auditing properties. However, you can modify the audit.alfresco-access.enabled=false and audit.cmischangelog.enabled=false propeties to enable/disable a particular audit application.
Generation of audit data is disabled by default. To enable auditing permanently, settings must be added to the Alfresco global properties file as shown in the following text. To enable auditing permanently, add the following setting to the file:

Auditing is enabled by default. To enable generation of audit data that you can view in Explorer or Share, you will need to enable the audit.alfresco-access.enabled property.

Once changes to the global properties file have been saved, you will need to restart the Alfresco server, for auditing to be fully enabled.

You can check the status of auditing conveniently from the command line by using a tool such as curl to access the Audit Control web script.

To check the global status of auditing issue a command, such as:

curl -u admin:password "http://localhost:8080/alfresco/service/api/audit/control"      

This invokes the web script with a GET request. This will result in a JSON response such as the following if auditing is currently enabled:

   "enabled" : true,
         "name": "Alfresco Tagging Service",
         "path" : "/tagging",
         "enabled" : true
         "name": "alfresco-access",
         "path" : "/alfresco-access",
         "enabled" : true

While this does return the global status of the auditing framework, audit data will only be generated if audit.alfresco-access.enabled is enabled.

Auditing can also be globally enabled or disabled using the control web script. To do this a POST request is sent to the web script. For example, using curl, auditing can be enabled using the following command:

curl -u admin:password -d "" "http://localhost:8080/alfresco/service/api/audit/control?enable=true"

This results in the following response:

   "enabled" : true

To disable auditing issue the following command:

curl -u admin:password -d "" "http://localhost:8080/alfresco/service/api/audit/control?enable=false"

This results in the following response:

   "enabled" : false

While the global status of the auditing framework can be switched on and off in this manner, audit data will only be generated if audit.alfresco-access.enabled is enabled in the global properties file.

Note: Enabling or disabling auditing using the Audit Control web script only remains valid in force while the server is running; the setting will not be retained following a server restart, but will subsequently be set according to the values in

Using JMX to control auditing

A JMX client can be used to access global properties. The properties can be modified using the JMX client. A server restart is not required for changes to properties to take effect.