ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Colm O hEigeartaigh <>
Subject Re: WSS4J Validators
Date Thu, 10 May 2012 09:21:40 GMT

The way to specify custom Validators is to have something like:

WSSConfig config = WSSConfig.getNewInstance();
WSSecurityEngine ret = new WSSecurityEngine();

You can see how CXF does it here:

Possibly Rampart isn't setting the WSSConfig instance on the security
engine or is not allowing the user to add or remove Validator
instances on it. Either way it's an issue for the Rampart team.


On Wed, May 9, 2012 at 8:00 PM, Graeme Jenkinson <> wrote:
> Hi,
> I recently built the Synapse-2.2.0-SNAHSOT in order to pick up the WSS4J 1.6
> improvements, specifically the Validator interface. However, using
> Synpase/Rampart I can't find anyway of actually getting hold of the
> WSSConfig instance to change the default Validators.
> In the pas t(under WSS4J 1.5.x)  I've provided a custom Processor by
> modifying the WSSConfig instance returned by WSSConfig.getDefaultWsConfig().
> However, under WSS4J 1.6.x this method has been removed. Am I missing an
> obvious way of changing the default Validator/Processor map returned by
> WSSConfig? As at the moment I can't see a way of changing those mappings
> under Rampart/Synapse.
> I suspect that this is a "Rampart issue", but as I not overly familiar with
> the code or the reasoning behind the changes to WSSConfig I though it best
> to consult WSS4J experts and then work from there.
> thanks,
> Graeme Jenkinson

Colm O hEigeartaigh

Talend Community Coder

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message