Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New XML Signing Options, extra tags to sign and small bug fix #1091

Merged
merged 3 commits into from
Oct 1, 2019

Conversation

LorneCurrie
Copy link
Contributor

Added new Signer Options to add a prefix to the signature tags added in WSSecurityCert
Added new Signer Options to add Attributes to the Signature tag added in WSSecurityCert
Updated the Readme file
Added tests
Change the join from /n to ' ' in client _invoke soapheaders.
The new line character stopped the XML from being decoded by a WSE SOAP server

Added new Signer Options to add prefix to signature tags added
Added new Signer Options to add Attributes to the Signature tag
Updated the Readme file
Added tests
change the join from `/n` to `' '` in client _invoke soapheaders.
The new line character stopped the XML from being decoded by a WSE system
@coveralls
Copy link

coveralls commented Oct 1, 2019

Coverage Status

Coverage increased (+0.03%) to 94.519% when pulling 99bb272 on LorneCurrie:update-for-WSE-SOAP-APIs into 827d5b5 on vpulim:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.03%) to 94.519% when pulling 407e167 on LorneCurrie:update-for-WSE-SOAP-APIs into 827d5b5 on vpulim:master.

@LorneCurrie
Copy link
Contributor Author

With regards to the change I made in src/client.ts, should I add this as a configurable option? When I added WS-Addressing headers I needed for my SOAP Requests, I was getting the following error: the signature or decryption was invalid. Turns out that the /n character was causing issues. When I replaced it with a empty whitespace, it worked.

@@ -864,6 +864,20 @@ WS-Security X509 Certificate support.
var privateKey = fs.readFileSync(privateKeyPath);
var publicKey = fs.readFileSync(publicKeyPath);
var password = ''; // optional password
var options = {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you add comments in this example to explain if these are optional and what they're for etc.?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Added Readme examples for the option added
Removed some extra XML tags added from a cut and paste error
@jsdevel jsdevel merged commit 9ad07cf into vpulim:master Oct 1, 2019
@jsdevel
Copy link
Collaborator

jsdevel commented Oct 1, 2019

thanks!

@LorneCurrie
Copy link
Contributor Author

@jsdevel when are you planning on doing the next release?

@jsdevel
Copy link
Collaborator

jsdevel commented Oct 16, 2019

@LorneCurrie published as 0.30.0

Danail-Irinkov pushed a commit to Danail-Irinkov/node-soap that referenced this pull request Jan 19, 2020
…#1091)

* New XML Signing Options, extra tags to sign and small bug fix

Added new Signer Options to add prefix to signature tags added
Added new Signer Options to add Attributes to the Signature tag
Updated the Readme file
Added tests
change the join from `/n` to `' '` in client _invoke soapheaders.
The new line character stopped the XML from being decoded by a WSE system

* Fixed small lint issues

* Added README examples

Added Readme examples for the option added
Removed some extra XML tags added from a cut and paste error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants