Wiki Article questions

[cracker_jack_04]

I am trying to get a SAML 2.0 implementation(Service Provider) done for a Seam Application that we have. I am following the wiki article
http://www.jboss.org/community/wiki/JBossSeamsupportforWebBrowserSSOProfile

I have a few questions

1) I made the modifications to the components.xml file and deployed the application. But the redirect when a protected page is requested is still to the .local login.seam page and not the Id provider's SSO page. This is because of the "login-view-id" configuration in the pages.xml page. Am I missing some other config parameter?

2) What is the URL to provide to the Id Provider to post back in the SAML Metadata xml file?

3) Does the implementation assume that the assertions are encrypted with the idProvider's private key?

My env : JBoss 4.2.2 + Seam 2.1.1 GA + JBoss Identity 1.0. Beta3

Thanks in advance.

[marcelkolsteren]

1)

Probably you're experiencing problems because the latest version of the article is based on the newest release of JBoss Identity (called picketlink) which is to be released soon. If you like to use the 1.0.0.beta3 version, use version 4 of the article. You can find it here:

http://www.jboss.org/community/wiki/JBossSeamsupportforWebBrowserSSOProfile/version/4

The changes with the latest version of the article (version 5) can be found here:

http://www.jboss.org/community/wiki/JBossSeamsupportforWebBrowserSSOProfile/diff?secondVersionNumber=5

2) You probably mean the URL of the Assertion Consumer Service? You can use http://www.yourserver.com/<app-root>/AssertionConsumerService.seam. In fact any URL that is picked up by the Seam servlet will do.

3) In components.xml, you can configure whether the Seam authentication filter should validate that the assertion contains a valid signature (signed with the private key of the IDP). You do this with the signatureRequired parameter (which is true by default). If signatureRequired is true, the parameters keyStoreURL, keyStorePass and idpCertificateAlias are used to locate the certificate of the IDP.

Hope this will help you. Your questions and the problems you experience indicate that version management for JBoss Identity is still to be improved. :-)