Exclusive Canonicalization nsCompare is not spec complaint and creates invalid digests about xml-crypto

[yaronn]

Hi @ddowhy - thanks for noticing that. I need to advise that it will take me a while to find the time for a deep investigation of this. It does seem a fix would be in the comparison methods. In case you now have a live service in a different platform which you cannot interoperate with would be great if you could tell if indeed a change there fixes it. I recommend to hard code your attributes into the comparison method you pasted, e.g.

if (a.prefix=="saml") && (b.prefox=="samlp") return 1

then you can force the canonical xml to come as you need and tell if this is indeed the issue.

[yaronn]

@ddowhy - thanks for the details defect submission! I've fixed this in version 0.1.24 and published to npm.

[dfloresgonz]

how did you solve it? SignedXml.prototype.getCanonXml changes the order of my attributes