[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1032) Integration with JBoss SSO

[Rich Nill (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-1032?page=comments#action_12401431 ] 
            
Rich Nill commented on JBSEAM-1032:
-----------------------------------

I wanted to understand if this feature request will handle the issue identified in: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=119389

Specifically, most web containers/app servers support third party authentication proxies that will provide a user principal to the web container.  For example, we use WebSphere Application Server and it supports the major authentication proxies (Oracle Access Manager (formerly Oblix), CA's Netegrity SiteMinder, IBM's TAM, etc.).  In this case, login occurs at the authentication proxy and the identity is passed to the web container.  Applications can use request.getUserPrincipal() and isUserInRole(), etc.

I would think that there would be support built into Seam to simply leverage the principal that is supplied (essentially delegating authentication to another provider).  By enabling this, you would automatically support a bunch of application servers and authentication proxies.

I was hoping this is the approach that will be taken.  Any thoughts?


> Integration with JBoss SSO
> --------------------------
>
>                 Key: JBSEAM-1032
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1032
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Security
>    Affects Versions: 1.2.0.GA
>            Reporter: Shane Bryzak
>         Assigned To: Shane Bryzak
>             Fix For: 2.1.0.GA
>
>
> We should provide integration of Seam Security with JBoss SSO.

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