[jbossseam-issues] [JBoss JIRA] Resolved: (JBSEAM-3249) Add bridge between Servlet Security and Identity component

[Dan Allen (JIRA)]

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

Dan Allen resolved JBSEAM-3249.
-------------------------------

    Resolution: Done


> Add bridge between Servlet Security and Identity component
> ----------------------------------------------------------
>
>                 Key: JBSEAM-3249
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3249
>             Project: Seam
>          Issue Type: Feature Request
>          Components: Security
>    Affects Versions: 2.0.3.CR1, 2.1.0.A1
>            Reporter: Dan Allen
>            Assignee: Dan Allen
>             Fix For: 2.0.3.CR2, 2.1.0.BETA1
>
>         Attachments: JBSEAM-3249.txt, JBSEAM-3249.txt
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Spring Security uses a security context integration filter that wraps the HttpServletRequest so that the security framework can respond to getUserPrincipal(), getRemoteUser(), and isUserInRole(). We should support this style of integration with our Identity component, especially since Seam prides itself on making standard Java EE stuff work. In fact, doing so is ridiculously easy.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira