Added support for token encryption on wsFed protocol #45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
add wreply parameter
… extract the saml:Assertion node
Configurable xpath to Signature, and extractor for saml:Assertion node
Updated to use Express ^4.11
…dAssertion elements
…g the assertion Updated error message Updated message and details Added comment
Improved getSamlStatus to return mark status:Responder as Error
Add fault check support
add license to package.json
Revert "add license to package.json"
Support passReqToCallback option.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Quick patch to support aes-256 encryption of SAML tokens for the wsfed protocol. Convention base for the private key: You must provide a cert at the root of you project in the certs folder named token-signing.key