You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "AilanChen (Commented) (JIRA)" <ji...@apache.org> on 2012/02/16 02:59:01 UTC
[jira] [Commented] (WSS-301) WSS4J 1.6 incorrectly using
XML-Security ResourceResolvers
[ https://issues.apache.org/jira/browse/WSS-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209067#comment-13209067 ]
AilanChen commented on WSS-301:
-------------------------------
Thanks to "GoAgent" that i can over the GFW than konw this iusse.
Lived in China was very tangle!
> WSS4J 1.6 incorrectly using XML-Security ResourceResolvers
> ----------------------------------------------------------
>
> Key: WSS-301
> URL: https://issues.apache.org/jira/browse/WSS-301
> Project: WSS4J
> Issue Type: Bug
> Affects Versions: 1.6.1
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Fix For: 1.6.2
>
> Attachments: wss4j-1.6.2-SNAPSHOT.jar
>
>
> WSS4J 1.6.x is incorrectly using XML-Security ResourceResolvers to "resolve" DOM Elements for use in signature creation and verification. WSS4J uses a custom IdResolver implementation to call a custom ResourceResolverSpi instance. This IdResolver implementation uses "internal" org.jcp.* classes, and this is causing problems when using JDK 1.6 for signature creation and validation in some containers (Jetty).
> WSS4J should be using the JSR-105 API instead to find and supply elements for signature/creation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org