You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by twilking <gi...@git.apache.org> on 2019/02/03 17:27:54 UTC
[GitHub] wss4j pull request #18: CustomTokenAction can now add any org.w3c.dom.Elemen...
GitHub user twilking opened a pull request:
https://github.com/apache/wss4j/pull/18
CustomTokenAction can now add any org.w3c.dom.Element to security header independent from implementation
When adding the custom token to security header the process tried to cast the provided object to com.sun.org.apache.xerces.internal.dom.NodeImpl. This behavior occurred a class cast action. Now only the org.w4c.dom.Element interface is used. The token is added by WSSecurityUtil.prependChildElement like in other action classes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/twilking/wss4j 2_2_x-fixes
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/wss4j/pull/18.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #18
----
commit 7a8fd95720e4f7b7c666e2e4d6d4f9fd7dda0c17
Author: Tim Wilking <ti...@...>
Date: 2019-02-03T17:16:11Z
CustomTokenAction can now add any org.w3c.dom.Element to security header independent from implementation
----
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
[GitHub] wss4j pull request #18: CustomTokenAction can now add any org.w3c.dom.Elemen...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/wss4j/pull/18
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org