3 Replies Latest reply on Dec 25, 2009 7:42 AM by marcelkolsteren

    idProvider initiated request - Seam integration

      I have a question regarding unsolicited idProvider initiated requests. Are they supported? I am using JBoss 5.0.1 & JBoss Identity 1.0.0 Beta1 with  a Seam 2.1.1 GA based app. I am trying to test out an id Provider initiated SSO request. After logging the user in, the SAMLAUthenticationFilter tries to redirect assuming there is a redirect URL stored in the Relay States. But, since the request is id Provider initiated there is none. I checked the code in the new picket link release and it seems to be doing the same. Is there any way to support an Id Provider initiated SSO request with JBoss-identity-seam ?

       

      Thanks in advance.

        • 1. Re: idProvider initiated request - Seam integration
          marcelkolsteren

          IDP initiated requests are not supported yet. You are right: the SAML authentication filter looks for a RelayState request parameter, and if it doesn't find one, it will throw a runtime exception.

           

          Maybe you could circumvent this problem by adding "?RelayState=1000" to the Assertion Consumer Service URL of your Seam SP (configured in your IDP). The next thing to ensure is that restoring relay state 1000 results in a redirect to the entry page of your Seam application. You could do that by creating an own version of the component "org.jboss.identity.seam.federation.relayStates". Create a copy of the JBoss Identity supplied component, and change the restoreState method so that index 1000 (corresponding to relay state 1000) is always redirected to the entry page of your application. Probably you need to add an @Install(precedence = Install.APPLICATION) to your copy of the component, in order to tell seam that it should instantiate your version.

          • 2. Re: idProvider initiated request - Seam integration
            anil.saldhana

            Please pick the latest PicketLink 1.0.0 release for your further work.

             

            Unsolicited IDP response to your Seam app should be a valid use case. In that case, I think a pre-established trust pattern between the client and the Service (based on the IDP assertion) should kick in IMO.

            • 3. Re: idProvider initiated request - Seam integration
              marcelkolsteren
              I created a JIRA feature request for this use case: https://jira.jboss.org/jira/browse/PLFED-1.