Closed joerglang closed 10 months ago
What version are you updating to? The 1.0.3 is essentially just a rename of the Kentor library and should work. The 2.9.2 has more changes.
We are updating from Kentor 0.21.2 to Sustainsys.Saml2 version 2.9.2
If you just want to get up to a supported version, I would recommend going to 1.0.3 instead. It is still supported and has much less changes than the 2.x line.
After changing back to 1.0.3 I get at least another error...
Sustainsys.Saml2.Exceptions.UnexpectedInResponseToException: Received message contains unexpected InResponseTo "id45527d80b3f44c9f82271f9bfd12f69d". No cookie preserving state from the request was found so the message was not expected to have an InResponseTo attribute. This error typically occurs if the cookie set when doing SP-initiated sign on have been lost.
I assume that this has to do with the app.UseKentorOwinCookieSaver();
that no longer exists.
I tried with asolutions for the problem I found in the internet (CookieManager = new SameSiteCookieManager(new SystemWebCookieManager())
) but this doesn't seem to solve the problem.
Yes, that issue could be caused by a lost correlation cookie yes.
If you want more hands on help on the upgrade, I do offer remote consulting services as part of the support package for Sustainsys.Saml2. Please reach out to support@sustainsys.com for more information.
We have used the Kentor library in our solution and wanted finally update to Sustainsys. We thought that would be not a big deal. But however we are stuck.
When we receive the Callback to AuthServices/Acs we get a NullReferenceException that. The code then never reaches our wired up
AcsCommandResultCreated
method.In the log I see
2024-01-07 16:11:31.119 +01:00 [Error] Saml2 Authentication failed. The received SAML data is
plus the SAML that was received that looks good to me. It is the same SAML that works when using the Kentor library.The SAML response is added below (sensitive information removed). The response comes from our own mock, that returns results identical to the real IdP that we cannot install localy as this is a government internal solution.
Can you point me in the direction I need to look? Any help is appreciated.