[jbossws-issues] [JBoss JIRA] (JBWS-3812) Incorrect value for ws-security.ut.validator
Alessio Soldano (JIRA)
issues at jboss.org
Thu Mar 12 18:08:19 EDT 2015
[ https://issues.jboss.org/browse/JBWS-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049631#comment-13049631 ]
Alessio Soldano commented on JBWS-3812:
---------------------------------------
OK, I've created https://issues.apache.org/jira/browse/CXF-6295 and committed a tentative fix on Apache CXF master. Thanks for the provider.
> Incorrect value for ws-security.ut.validator
> --------------------------------------------
>
> Key: JBWS-3812
> URL: https://issues.jboss.org/browse/JBWS-3812
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf
> Affects Versions: jbossws-cxf-4.2.4
> Reporter: John Ament
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-5.0
>
>
> I found a forum post indicating that this value should work, in my hunt to make security work in WildFly. https://community.jboss.org/thread/229071
> When you set the parameter ws-security.ut.validator in jaxws-endpoint-config.xml, the value that gets set is in fact the string value, e.g. com.mycompany.cxf.validators.MySpecialValidator
> CXF is expecting that this is an instantiated instance of the class, not a classname. It results in a ClassCastException. You can see here for reference: http://cxf.apache.org/docs/ws-securitypolicy.html look under Validator implementations.
> To work around this, you can register a custom InInterceptor and set the value in the message context. It's not ideal, but you could read the value from jaxws-endpoint-config.xml and instantiate that class, passing it back to the message context.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the jbossws-issues
mailing list