Hi, Some validation fails at Service Provider (SP) side and it's difficult to deduce what fails from that trace file.
Here's a wild guess: Is assertion signature validation enabled at SP? If yes, you have to enable Assertion Signing at the Identity Provider side (returned SAMLResponse didn't have the Assertion signed). You will see this option when you visit the SAML SSO Service Provider Registration page in WSO2 Identity Server. Thanks & Regards Dulanja On Wed, Dec 11, 2013 at 1:41 PM, Nisreen123 <[email protected]> wrote: > Hi all; > I am trying to implement SAML SSO between two different instances of IBM > websphere WAS servers, the WAS servers will act as the service providers > where the WSO2 will work as the identity provider , I configured the > service > providers in WSO2 v 4.6. When I enter the protected resource at the WAS > service provider I get redirected to the idp login page, but when I enter > the credentials, the page tells me that I am redirected to the SAML ACS but > nothing happen and the page keeps refreshing itself, I have attached the > trace file. Can anyone help me with this? > trace.txt > <http://wso2-oxygen-tank.10903.n7.nabble.com/file/n89582/trace.txt> > > > > -- > View this message in context: > http://wso2-oxygen-tank.10903.n7.nabble.com/SAML-SSO-between-WSO2-and-IBM-WAS-servers-tp89582.html > Sent from the WSO2 Development mailing list archive at Nabble.com. > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Dulanja Liyanage Senior Software Engineer - WSO2 Inc. M: +94776764717
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
