[jboss-jira] [JBoss JIRA] (ELY-37) Audit Logging Integration

[David Lloyd (JIRA)]

    [ https://issues.jboss.org/browse/ELY-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177659#comment-13177659 ] 

David Lloyd edited comment on ELY-37 at 3/16/16 8:34 AM:
---------------------------------------------------------

We have determined that the following events should be supported:
* Authentication initiated
* Authentication succeeded
* Authentication failed
* Authentication incomplete
* Authorization check succeeded
* Authorization check failed

In addition, a session login/logout API should be made available (details forthcoming).



was (Author: dmlloyd):
We have determined that the following events should be supported:
* Authentication initiated
* Authentication succeeded
* Authentication failed
* Authentication abandoned
* Authorization check succeeded
* Authorization check failed

In addition, a session login/logout API should be made available (details forthcoming).


> Audit Logging Integration
> -------------------------
>
>                 Key: ELY-37
>                 URL: https://issues.jboss.org/browse/ELY-37
>             Project: WildFly Elytron
>          Issue Type: Task
>          Components: API / SPI, Audit
>            Reporter: Darran Lofthouse
>            Assignee: Jan Kalina
>             Fix For: 1.1.0.CR1
>
>
> Implement into Elytron samething like:
> https://github.com/picketbox/picketbox/tree/master/security-spi/spi/src/main/java/org/jboss/security/audit
> or
> https://github.com/wildfly/wildfly-core/tree/master/controller/src/main/java/org/jboss/as/controller/audit
> or
> https://github.com/kabir/tamper-detecting-audit-log
> UPDATE:
> By discussion should be based on currently not implemented processing of **security events** - depends on it from now.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)