Eduardo Mourão wrote on 2009-07-30:
> Well, I have a signed XML that I would really appreciate if you people can
> tell me if it's signature is valid or not.
It's not even valid XML as attached, so my guess is you corrupted it
somehow.
> I'm really running out of options. Out partner did set
> X
Well, I have a signed XML that I would really appreciate if you people can
tell me if it's signature is valid or not.
I'm really running out of options. Out partner did set
XmlDocument.PreserveWhitespace = true and that was my last resort.
Our validator says it is completely valid, but our .NET
Scott Cantor wrote:
Inconsistent c14n has caused us to have validation failures in the past,
and
I have found no decent way to finding out what exactly the canonicalizer
output looks like. I've had to use the debugger and set the "os" stream to
a
FileOutputStream in DOMReferen
> Inconsistent c14n has caused us to have validation failures in the past,
and
> I have found no decent way to finding out what exactly the canonicalizer
> output looks like. I've had to use the debugger and set the "os" stream to
a
> FileOutputStream in DOMReference.transform(Data, XMLCryptoContex
this would be allowed. This would go a long way in helping understand why
validation of a message failed.
Thoughts?
Eduardo Mourão
07/24/2009 11:55 AM
Please respond to
security-dev@xml.apache.org
To
security-dev@xml.apache.org
cc
Subject
Re: Canonicalization Validation
Unfortunel
2009 12:55 PM
To: security-dev@xml.apache.org
Subject: Re: Canonicalization Validation
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
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.
