You are viewing the Kantega SSO legacy documentation. The new documentation site is: https://kantega-sso.atlassian.net/wiki/x/hwAb
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

To enable audit logging, you will have to turn it on in your logging configuration. Both successful and failed Kerberos and SAML logins will be logged. For failed logins, there will be an additional sentence explaining why it failed. By adding the two lines, you will get logging in a similar pattern as the security logging in Jira (as Jira has the most precise logging of logins).

Logging will look like this:

The user 'johndoe' has PASSED authentication using Kerberos
The user 'john.doe@mycompany.com' has PASSED authentication using SAML

Enabling in Confluence

This is done in Confluence by adding the following two lines below in the bottom of the file:
<confluence-binaries>/confluence/WEB-INF/classes/log4j.properties

log4j.logger.com.kantegasso.AuditLog = INFO, confluencelog
log4j.additivity.com.kantegasso.AuditLog = false

Log will be written to: atlassian-confluence.log

Enabing in Jira

This is done in Jira by adding the following two lines below in the "# Security logs" section in the file:
<jira-binaries>/atlassian-jira/WEB-INF/classes/log4j.properties

log4j.logger.com.kantegasso.AuditLog = INFO, securitylog
log4j.additivity.com.kantegasso.AuditLog = false

Log will be written to: atlassian-jira-security.log

Enabling in other Atlassian products

Similarly you may enable audit logging in other Atlassian products. Please contact us if you have problems setting this up and we will help you out.


This feature was added in version 3.5.15.

  • No labels