First, you should know that if your partner's validator removes whitespace from
the signed document (in most contexts) before attempting to validate the
signature, it does not conform to the digital signature specification. The
canonicalization spec is very clear that most whitespace must be ret
Unfortunely I don't have access to change the .NET signature validator.
I beleive the white spaces are, in fact, the problem. The only solution I
have in mind is make my signature validation act as the .NET validation.
How can I validate the canocalization of this document?
Eduardo Mourão
SEFI
This sounds a lot like an issue that made me nuts a couple of weeks ago. By
default, the .NET framework's XmlDocument.LoadXml() discards whitespace. Your
partner will need to set XmlDocument.PreserveWhitespace = true before loading
the document.
If they're already doing that, I haven't a clue.
Hi,
I'm having problems with .NET interoperability. My software receives signed
XML documents and validates them, but, when I send to one of our partners (a
.NET solution) it returns that the signature is not valid.
I took a look at those XML files and noticed that all the rejected files and
not
