Permission to generate audit log report in ACS commons for non admin users

Hi @abbirami,

1. Grant Access to Audit Log Nodes

I think Audit logs are stored under:

/var/audit

Permissions needed on /var/audit:

• jcr:read – Allows reading audit log entries.

You can assign this via user/group permissions.

2. Grant Access to the Audit Log Report Tool

The tool lives under:

/apps/acs-commons/components/audit-log-report

or if you're using the ACS Commons tools UI:

/apps/acs-commons/components/utility/audit-log-report

Permissions needed:

• jcr:read on:

  • /apps/acs-commons

  • /libs/acs-commons (if applicable)

• jcr:read on the nodes where the tool UI is rendered (often under /content, e.g., /content/acs-commons)

3. Access to Query Audit Logs (Optional but Important)

If you're using the ACS Commons Audit Log Report UI that queries audit data, make sure the group has access to the QueryBuilder service or permissions to run queries via /bin/querybuilder.json.

Path:

• /bin/querybuilder.json

• Permission: read + ability to post queries depending on UI behavior.

4. Allow Execution of Audit Log Report Servlet (if applicable)

Some versions of ACS Commons expose the report via a servlet, like:

/bin/acs-commons/audit-log-report

Permissions:

• Grant jcr:read and allow access to /bin/acs-commons or the servlet path.

5. General Permissions Needed for Viewing ACS Tools:

• jcr:read on /apps/acs-commons

• jcr:read on /etc/acs-commons (some config may be here)

• jcr:read on /libs/granite/ui

• jcr:read on /libs/cq/core/content/tools (if part of classic UI)

Hope this helps!