srd90
srd90
>in the .d.ts it is marked as static > >static CanonicalizationAlgorithms: { [uri: string]: new() => TransformationAlgorithm }; >static HashAlgorithms: { [uri: string]: new() => HashAlgorithm }; >static SignatureAlgorithms: {...
If you are looking something like this * https://github.com/node-saml/xml-crypto/pull/471 i.e. to be able to use those algorithms easily in your own code I would suggest you to help maintainer(s) to...
Are you aware that this repository has [discussions](https://github.com/node-saml/xml-crypto/discussions) section activated? IMHO all of these could have been started as questions at discussions instead of issues: * https://github.com/node-saml/xml-crypto/issues/479 * https://github.com/node-saml/xml-crypto/issues/480 *...
Are you after this pending/work in progress enabler: * https://github.com/node-saml/xml-crypto/issues/463 * https://github.com/node-saml/xml-crypto/pull/464 Quote from https://github.com/node-saml/xml-crypto/issues/463 : >... >Adding a `Reference` to each part of the document to be signed is...
>does we have a solution for this ? Where are you point with this question's `this`? If your question's `this` point to this: https://github.com/node-saml/xml-crypto/issues/463 then you have some initial version...
IMHO this issue could be closed because this is actually duplicate of/work in progress in: * https://github.com/node-saml/xml-crypto/issues/463 * https://github.com/node-saml/xml-crypto/pull/464
Are you aware that this repository has [discussions](https://github.com/node-saml/xml-crypto/discussions) section activated? IMHO all of these could have been started as questions at discussions instead of issues: * https://github.com/node-saml/xml-crypto/issues/479 * https://github.com/node-saml/xml-crypto/issues/480 *...
IMHO this issue can be closed because this is actually "part of" problem described at issue: * https://github.com/node-saml/xml-crypto/issues/481 which in turn is duplicate of * https://github.com/node-saml/xml-crypto/issues/463 * which is being...
>do you have an idea why java signature has #xD;\n ? Yes. At least I have an idea. Dunno about others. BTW. You considered this to be a bug at...
In case your JDK version was some of those affected by following: * https://bugs.openjdk.org/browse/JDK-8264194 * https://github.com/node-saml/node-saml/issues/242#issuecomment-1374056961 * also follow link from aforementioned comment to keycloak side issue and read through...