By vijay - 10/31/2022
We recently finished converting our system from .net 4.7.2 to core .net 3.1
As a result we had to update our Component Space Library to Core.Net as well
But after going to Prod one of our 3rd parties that use SSO is no longer able to login into our system
We expected everything to work seamlessly but they are not able to use our system any more and we are getting this error
2022-10-31 22:18:12.204 -04:00 [DBG] The HTTP request is unrecognized. 2022-10-31 22:18:12.205 -04:00 [DBG] HTTPS request: GET /Account/AssertionConsumerService HTTP/1.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9 Connection: keep-alive Host: echelon.razorplan.com User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36 Accept-Encoding: gzip, deflate, br Accept-Language: en-CA,en-GB;q=0.9,en-US;q=0.8,en;q=0.7 Cookie: ajs_anonymous_id=bd067aea-8aeb-4e16-8e1b-74d68d888507; _hjSessionUser_917692=eyJpZCI6ImFlZWViNDhjLTU5MjktNTNkNi05ZGQxLTBjNTc3OTRhZTFkYyIsImNyZWF0ZWQiOjE2NTExNjAxNTY4ODIsImV4aXN0aW5nIjp0cnVlfQ==; saml-session=32b8112f-9a09-4b66-830a-7955290cdd8e; .AspNetCore.Session=CfDJ8P8P%2BDF6%2Fq1EhLcp8MOiKMGz%2B0Zg9uywvqdvH9186ycnS%2FJVthTozLFsr68z7nDBDQq%2BgPAjvwDieUYhqGQOLdPrx9LxSmIkHs0lmRKY3dEfU5uYoIaeLdl%2BVGy%2BKzDqxi2ag%2BuHYes6fO%2F9D6yqSLnnCdXsGRtkbOTZ6IOOH%2BWH; .AspNetCore.Antiforgery.dERNBXus2Y8=CfDJ8P8P-DF6_q1EhLcp8MOiKMHWEChPOSefDV-D3lVWuVn4dJvwQb4HlveufI7DSCvA_7mi0F1jsr_vR6BP9vOIs6nh0X9PbNKRLVfwX0l8Jnq9cI5D1xOUSDybLYPDXt56MLNBs3rGE972P2LFaCvB2MY; mp_bfad3bfd476350b99fbace1bb4f4f1c2_mixpanel=%7B%22distinct_id%22%3A%20%22183ece3608b1bb-0e8005b72aa403-26021f51-1fa400-183ece3608c282%22%2C%22%24device_id%22%3A%20%22183ece3608b1bb-0e8005b72aa403-26021f51-1fa400-183ece3608c282%22%2C%22%24initial_referrer%22%3A%20%22https%3A%2F%2Fsystem.razorplan.com%2FCustomplan%2FHome%22%2C%22%24initial_referring_domain%22%3A%20%22system.razorplan.com%22%7D; _ga=GA1.2.975180360.1667147252; _gid=GA1.2.1497647150.1667147252 Upgrade-Insecure-Requests: 1 sec-ch-ua: "Chromium";v="106", "Google Chrome";v="106", "Not;A=Brand";v="99" sec-ch-ua-mobile: ?0 sec-ch-ua-platform: "Windows" sec-fetch-site: none sec-fetch-mode: navigate sec-fetch-user: ?1 sec-fetch-dest: document MS-ASPNETCORE-TOKEN: 48ff1301-5a09-4a9e-903d-828a16d02c8c X-Original-Proto: http X-Original-For: 127.0.0.1:54195 2022-10-31 22:18:12.205 -04:00 [ERR] Receiving an SSO response from a partner identity provider has failed. ComponentSpace.Saml2.Exceptions.SamlBindingException: A SAML message cannot be received as the HTTP request is unrecognized. at ComponentSpace.Saml2.SamlProvider.ReceiveMessageAsync() at ComponentSpace.Saml2.SamlServiceProvider.ReceiveSsoAsync() 2022-10-31 22:18:12.206 -04:00 [ERR] Uncaught Assetion Exception.
The only thing we had changes is the application URL. When we created the certificate we used a different DNS name
$date_now = Get-Date $extended_date = $date_now.AddYears(5) $cert = New-SelfSignedCertificate -certstorelocation cert:\localmachine\my -dnsname system.razorplan.com -notafter $extended_date -KeySpec KeyExchange $pwd = ConvertTo-SecureString -String '*******' -Force -AsPlainText $path = 'cert:\localMachine\my\' + $cert.thumbprint Export-PfxCertificate -cert $path -FilePath C:\Users\Public\Documents\ech.pfx -Password $pwd
The certificate we gave them was system.razorplan.com, but now the app URL has been changed to ech.razorplan.com. Will the DNS name be an issue to cause this error in the cert? Any suggestions on how to debug this?
|
By jubar - 5/22/2023
+xThanks, That was the issue. Appreaciate your reply Apologies, were you able to resolve this in your system, or did you have to involve the 3rd party?
Thanks, Milos
|
|