I am creating a SAML IDP to handle SSO among a student portal, and a third party The system is based on my code, and I have used some of my unintended libraries in my project. I have also set up my sample identification provider to make it easier to debug this problem.
To handle the authentication, I take a GUID from the Student Portal on the basis of this page, used by the student to get the details of an internal service and package it in a SAML claim , Which is again signed with the x.50 9 certificate before sending it to third party SAML service provider. It's here that I'm stuck. When I try to sign the SAML request:
Which debugging and research I've done, indicates that the code is not a problem, but just you I can understand how I found here: is coming from ComputeSignature () , which is being said to, which is being said indirectly.
Before I attempt to sign the package. I have tested it well and have run it through debuggers without finding any problem with it.
My hypothesis is that there is something wrong with the certificate, which is signed for its own testing purposes, the company I am working with assures me that the other people who have integrated They used exams in the past, but I can think of any other reason why it would be unsuccessful. Although I have tried many changes, I think the most likely to prepare a work test certificate based on my research is: makecert.exe -a md5 -r -pe -n "CN = iGradTest" My RSS-SR Localmachine - A sign "c: \ iGradTest.cer" , but the same problem for issuing the resulting certificate is the same problem. The generated certificate has been given a friendly name and has been established to work with IIS. The Winhttpcertcfg app is successfully receiving the certificate, but failed to add it when claiming it.
I am at a loss for what to do next. Any suggestions on the next steps will be highly appreciated for identifying and solving this issue. Thanks for taking the time to read.
The exception that you are experiencing means that refers to the URI Based on the code provided, a # for the SAML20Assertion.cs: 90 ID does not resolve the element marked with a id attribute
Prepending, then the certificate utility CCS: 69 is preparing it again, remove it from any one place, and everything is fine.
SAML20Assertion.cs: 90:
Certificate Availability AppendSignatureToXMLDocument (ref xmlResponse, "#" + ((AsserttionType) response. ITIs [0]). ID, signing code; should be
certificate utility AppendSignatureToXMLDocument (Ref XML Response, (Response Type) Response. Items [0]). ID, SigningCurrent; 
Comments
Post a Comment