Chris Barth

The first step would be to see if NodeJS supports this. If so, then you can easily put up a PR that mimics the existing methods for doing this. If...

In that case you might just use the plugable nature of this library to add such support yourself. There should be information in the README on that.

If you'd like to add support for custom signing methods to `node-saml`, I'd be happy to look at that. This way you could just pass your function through `node-saml` to...

@niladrinic , I've pretty printed your code and used properly labeled fences to make it much easier to read. After pretty printing the XML, it appears that both are the...

I am sorry that you're having issues. We certainly want to fix them, however, we don't have enough information to help. The original post lists the expected output as the...

@srd90 your sample code here gives a lot to go on, and I'm glad you were able to find this. @niladrinic , @CarlaMck77 , @cfficaurzua , if any of you...

@bjrmatos @yaronn , instead of hard-coding something and maintaining a fork, would you consider creating a PR with a test suite so that the community can benefit?

`getKeyInfoContent` is now a `noop` by default. This will show in the next semver-major release.

> > By that logic you should also resolve the `SecurityTokenReference` when in `wssecurity` mode. > > https://docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-pr-x509TokenProfile-01.htm Feel free to submit a PR.

@alphanso , I'm very glad you found and fixed your issue. To help the community benefit from your efforts, would you consider creating a PR with a test suite and...