Deploy an sp application and initially access a protected page which is NOT the welcome page. create two security domains <security-domain name="sp" cache-type="default"> <authentication> <login-module code="org.picketlink.identity.federation.bindings.jboss.auth.SAML2LoginModule" flag="required"/> </authentication> </security-domain> <security-domain name="idp" cache-type="default"> -> use a login module of your choose, I used LdapExtended Deploy the attached idp.war and sp.war Run the server listening to "localhost" access: http://localhost:8080/plhello/test/test.jsp -> redirect to IDP -> login -> redirects to http://localhost:8080/plhello/ -> shows http://localhost:8080/plhello/index.jsp this worked fine in EAP 6.1.1, the resulting page was http://localhost:8080/plhello/test/test.jsp
Created attachment 876401 [details] sp war file
Created attachment 876402 [details] idp war file
Seems as a duplicate of bug#1071288
jcacek seem to be right. Also, Im not able to reproduce with current 6.x(though wild stroke of bad luck, first attempt was a success... ). Im going to close this as duplicate with proper milestone and version update. If this BZ is for 6.2 please issue new one, without 6.3 flag :) NOTE: could not reproduce with 6.x and 6.2.x current HEAD. *** This bug has been marked as a duplicate of bug 1071288 ***