0
votes

I am new to WSO2 and I follow this post to enable Single Sign On (SSO) for the following scenario:

  • Virtual machine running centos (IP: 192.168.0.18)
  • WSO2 IdentityServer 4.1.0 installed with https port: 9443
  • WSO2 ApplicationServer 5.1.0 installed with https port: 9443

Here is the problem:

  • when I access the application server console management, I am redirected to the identity provider login page as expected and I can login.

  • I am then redirected to the initial request (Application Server MGT Console) but a message appears telling me that the Authentication/Authorization fails.

In log files I can see following error:

TID: [0] [AS] [2013-05-14 16:13:32,128] INFO {org.wso2.carbon.identity.authenticator.saml2.sso.common.builders.AuthenticationRequestBuilder} - Building Authentication Request {org.wso2.carbon.identity.authenticator.saml2.sso.common.builders.AuthenticationRequestBuilder} TID: [0] [AS] [2013-05-14 16:13:32,388] ERROR {org.wso2.carbon.identity.authenticator.saml2.sso.util.Util} - Content is not allowed in prolog. {org.wso2.carbon.identity.authenticator.saml2.sso.util.Util} TID: [0] [AS] [2013-05-14 16:13:32,389] ERROR {org.wso2.carbon.identity.authenticator.saml2.sso.SAML2SSOAuthenticator} - System error while Authenticating/Authorizing User : Error occured while processing saml2 response {org.wso2.carbon.identity.authenticator.saml2.sso.SAML2SSOAuthenticator} org.wso2.carbon.identity.authenticator.saml2.sso.SAML2SSOAuthenticatorException: Error occured while processing saml2 response at org.wso2.carbon.identity.authenticator.saml2.sso.util.Util.unmarshall(Util.java:87) at org.wso2.carbon.identity.authenticator.saml2.sso.SAML2SSOAuthenticator.login(SAML2SSOAuthenticator.java:64) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

I search the net for this error but I was not able to find something that could help me to solve this problem.

Any help is welcome.

Thanks.

1

1 Answers

0
votes

this is due to a version difference between the SAML components being used in the two servers. We will make a public patch available.