[jboss-jira] [JBoss JIRA] (WFLY-487) Verify audit implications and required APIs

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFLY-487:
----------------------------------
    Fix Version/s: 10.0.0.Alpha2
                       (was: 10.0.0.Alpha1)


> Verify audit implications and required APIs
> -------------------------------------------
>
>                 Key: WFLY-487
>                 URL: https://issues.jboss.org/browse/WFLY-487
>             Project: WildFly
>          Issue Type: Sub-task
>          Components: Domain Management, Security
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>              Labels: authentication_service
>             Fix For: 10.0.0.Alpha2
>
>
> Auditing may be logging as the user that executes a request, if we have used a trust relationship for a request to be run as a different user we need to be able to track back to identify how the user for the request was selected.
> i.e. If userA runs something as userB and does something bad we must be able to track back that it was userA making the overall request without userB getting the blame.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)