Hi Berin,
you're absolutely right, and I understand it. If it was a requirement to
use CDATA tags for text nodes, we wouldn't have such problems. All other
contents could be considered subject to change. However, i'm using
Castor and it seems that the deserialisation process (marshalling)
rem
Mike Haller wrote:
i don't know why Canonicalization doesn't address this problem at all.
It sounds like being incomplete to me. One the one hand, there is taken
effort to "normalize" the XML document so it can be signed to
avoidproblems with formattings - on the other hand something simple li
Yes Berin, thanks,
i don't know why Canonicalization doesn't address this problem at all.
It sounds like being incomplete to me. One the one hand, there is taken
effort to "normalize" the XML document so it can be signed to
avoidproblems with formattings - on the other hand something simple li
Mike Haller wrote:
But after some marshalling/unmarshalling with Castor, the resulting
Document has no newlines any more, hence the SignatureValue of the
SignedInfo element is invalid.
How do I tell XMLSignature to add newlines into the SignedInfo before
validation? Or should I remove the ne
Hi,
in hope this is the correct mailing list, here my question:
Signing works, verification works.
But after some marshalling/unmarshalling with Castor, the resulting
Document has no newlines any more, hence the SignatureValue of the
SignedInfo element is invalid.
How do I tell XMLSignature
Hi,
I'm signing an xml document using hmac-sha1. I was just wondering what do people normally fill in for the element? I assume that you don't incorporate this element into the document because you can't/shouldn't store the secret in it. Or is there some way to incorporate this information
