Re: Canonicalization support

["João M. S. Silva" <jo...@gmail.com>]

Hi,

One more related question: how can Santuario deal with the fact that base64
text nodes are parsed by Xerces with whitespace being modified (normalized?)

Because, the sender signed the message with a specific whitespace
configuration. If Santuario receives a different whitespace configuration,
the digest won't match.

I can't see an option in Xerces to keep whitespace in base64 text nodes
(I've also asked in the mailing list) so there must be a way this issue is
worked around?

Having base64 text in XML is not that uncommon, so there must be a way to
deal with this?

Thanks.

João M. S. Silva


On Tue, May 28, 2019 at 2:09 PM Cantor, Scott <ca...@osu.edu> wrote:

> On 5/24/19, 12:14 PM, "João M. S. Silva" <jo...@gmail.com>
> wrote:
>
> > Is this mapped somewhere?
>
> It's literally defined in the XML Signature and Encryption specifications.
> The URIs are what those documents say they are.
>
> -- Scott
>
>
>

Re: Canonicalization support

["Cantor, Scott" <ca...@osu.edu>]

On 6/7/19, 3:04 PM, "João M. S. Silva" <jo...@gmail.com> wrote:

> One more related question: how can Santuario deal with the fact that base64 text nodes are parsed by Xerces with
> whitespace being modified (normalized?)

It can't, you can't normalize.

> I can't see an option in Xerces to keep whitespace in base64 text nodes (I've also asked in the mailing list) so there must
> be a way this issue is worked around?

Normalization is an option, and only applies to schema validation, IIRC.

-- Scott