[ https://issues.jboss.org/browse/TEIID-3595?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3595: --------------------------------------- The possible events are: login attempt - an issue we have here is providing a concise set of information to the audit event. No session and potentially no VDB has been identified at this point. The alternative information set would be - vdbName, vdbVersion, authType, userName, applicationName, properties login success - we can just update the auditmessage to provide the session login fails - somewhat similar to login attempt as this could be due to an invalid vdb or auth failure logout - similar to success and can provide the session So the question would be do we do attempt/success/fail or just success/fail. And then do we heavily extend the auditmessage to accomodate login attempt/fail, create a new message type, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)