ComponentSpace

Forums



SSO Random Error - SP initial SSO


SSO Random Error - SP initial SSO

Author
Message
mlam
mlam
New Member
New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)

Group: Forum Members
Posts: 15, Visits: 31
Hi 

There is a random element, we can login to their SSO and sometimes we can login and sometimes we can’t.

We build the logic the following for our SSO mobile apps. First, we open the browser that remove cache and cookie. Then, we (SP) will initial SSO by call the IDP. We the suppress basic Auth popup with Request URL looking like this https://username:password@idp.idpwebsite.com/... .on the Idp landing page (we use the user name and password that we received from our SP page to create that URL). On this page (Idp page) the user will key-in the user name and password. Once user name and password verified. It will come back to AssertionConsumerService page and we will log them into our system.

For the first time, everything working fine for the process above. But, when we logout the user from our site and repeat the progress above on the same browser. Sometime we retrieve error below on the AssertionConsumerService page

ComponentSpace.SAML2 Verbose: 0 : 4932/22: 08/03/2019 21:07:21: The decoded base-64 string is: <samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" ID="s2d635cb01e17dcd5049ca4a901ee122caeeecaffd" InResponseTo="_c60f3d52-5aa3-4d66-aa99-17b8979b9860" Version="2.0" IssueInstant="2019-03-08T21:00:52Z"><saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">nqc</saml:Issuer><samlp:Status xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol">
<samlp:StatusCode xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" Value="urn:oasis:names:tc:SAML:2.0:status:Responder">
</samlp:StatusCode>
</samlp:Status></samlp:Response>
ComponentSpace.SAML2 Verbose: 0 : 4932/22: 08/03/2019 21:07:21: Received SAML message: <samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" ID="s2d635cb01e17dcd5049ca4a901ee122caeeecaffd" InResponseTo="_c60f3d52-5aa3-4d66-aa99-17b8979b9860" Version="2.0" IssueInstant="2019-03-08T21:00:52Z"><saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">nqc</saml:Issuer><samlp:Status xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol">
<samlp:StatusCode xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" Value="urn:oasis:names:tc:SAML:2.0:status:Responder">
</samlp:StatusCode>
</samlp:Status></samlp:Response>
ComponentSpace.SAML2 Verbose: 0 : 4932/22: 08/03/2019 21:07:21: Received response over HTTP POST, samlMessage=<samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" ID="s2d635cb01e17dcd5049ca4a901ee122caeeecaffd" InResponseTo="_c60f3d52-5aa3-4d66-aa99-17b8979b9860" Version="2.0" IssueInstant="2019-03-08T21:00:52Z"><saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">nqc</saml:Issuer><samlp:Status xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol">
<samlp:StatusCode xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" Value="urn:oasis:names:tc:SAML:2.0:status:Responder">
</samlp:StatusCode>
</samlp:Status></samlp:Response>, relayState=
ComponentSpace.SAML2 Verbose: 0 : 4932/22: 08/03/2019 21:07:21: SAML message received: partner=nqc, message=<samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" ID="s2d635cb01e17dcd5049ca4a901ee122caeeecaffd" InResponseTo="_c60f3d52-5aa3-4d66-aa99-17b8979b9860" Version="2.0" IssueInstant="2019-03-08T21:00:52Z"><saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">nqc</saml:Issuer><samlp:Status xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol">
<samlp:StatusCode xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" Value="urn:oasis:names:tc:SAML:2.0:status:Responder">
</samlp:StatusCode>
</samlp:Status></samlp:Response>, relay state=
ComponentSpace.SAML2 Verbose: 0 : 4932/22: 08/03/2019 21:07:21: The SAML response doesn't include a destination.
ComponentSpace.SAML2 Verbose: 0 : 4932/22: 08/03/2019 21:07:21: Exception: ComponentSpace.SAML2.Exceptions.SAMLErrorStatusException: An error SAML response status was received. urn:oasis:names:tc:SAML:2.0:status:Responder
ComponentSpace.SAML2 Verbose: 0 : 4932/22: 08/03/2019 21:07:21:  at ComponentSpace.SAML2.InternalSAMLServiceProvider.ProcessSAMLResponse(XmlElement samlResponseElement, Boolean& isInResponseTo, String& authnContext, String& userName, SAMLAttribute[]& attributes)
 at ComponentSpace.SAML2.InternalSAMLServiceProvider.ReceiveSSO(HttpRequestBase httpRequest, Boolean& isInResponseTo, String& partnerIdP, String& authnContext, String& userName, SAMLAttribute[]& attributes, String& relayState)
 at Aura.Supersite.WebHost.Controllers.SSOController.<AssertionConsumerService>d__4.MoveNext() i

Any idea

Thanks
M Lam
ComponentSpace
ComponentSpace
ComponentSpace Development
ComponentSpace Development (3.2K reputation)ComponentSpace Development (3.2K reputation)ComponentSpace Development (3.2K reputation)ComponentSpace Development (3.2K reputation)ComponentSpace Development (3.2K reputation)ComponentSpace Development (3.2K reputation)ComponentSpace Development (3.2K reputation)ComponentSpace Development (3.2K reputation)ComponentSpace Development (3.2K reputation)

Group: Administrators
Posts: 2.2K, Visits: 5.9K
You've receiving a SAML response with a generic "urn:oasis:names:tc:SAML:2.0:status:Responder" error status.
You need to ask the IdP to take a look at their logs for more detailed information.

Regards
ComponentSpace Development
GO


Similar Topics


Execution: 0.000. 6 queries. Compression Enabled.
Login
Existing Account
Email Address:


Password:


Social Logins

Select a Forum....









Forums, Documentation & Knowledge Base - ComponentSpace


Search