[jboss-jira] [JBoss JIRA] Resolved: (JBID-161) Support for Seam Service Providers

Sun Aug 9 14:47:29 EDT 2009

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

Marcel Kolsteren resolved JBID-161.
-----------------------------------

    Fix Version/s: IDFED-1.0.0.beta1
       Resolution: Done


> Support for Seam Service Providers
> ----------------------------------
>
>                 Key: JBID-161
>                 URL: https://jira.jboss.org/jira/browse/JBID-161
>             Project: JBoss Identity
>          Issue Type: Feature Request
>          Components: Identity-Federation
>    Affects Versions: IDENTITY-1.0.0.alpha5
>            Reporter: Marcel Kolsteren
>            Assignee: Anil Saldhana
>             Fix For: IDFED-1.0.0.beta1
>
>
> Seam applications can already play the role of SAMLv2 Service Providers, by using the Tomcat SP valves supplied by JBID:
> http://www.jboss.org/community/wiki/SeamIntegrationWithJBossIdentity
> The disadvantage of this solution is that it relies on servlet security mechanisms that need to be specified in web.xml.
> In order to improve the ease of integrating Seam applications with JBID (for the Service Provider part), a specific Seam binding needs to be added to JBID. This binding should at least support the SP part of the Web Browser SSO Profile, using the HTTP-POST binding for authentication requests as well as for authentication responses. It should also support validation of message-level signatures received from the IDP.

-- 
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