Make whitespace in created signature node configurable option because of C# DOTNET signature validation #248
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.
I've created my fork after many hours spent on debugging.
I've extended constructor with new default properties:
I am not quite happy with implementation because it does not follow general whitespace configuration of
DOMDocument
object eg. this would be more straight forward to read:This is unfortunately not possible since
XMLSecurityDSig
object transforms signature template viaDOMDocument
to xml in it's constructor.This is related to:
Looking forward to change PR if necessary to better incorporate it in
xmlseclibs
package.