It appears the properties are not set right,
serviceProperties.put("ws-security.validate.token", "false");
moves the chain to a different path, so for using a CustomValidator the
above property will need to be dropped
Sergey
On 16/02/12 14:48, Colm O hEigeartaigh wrote:
Are you still getting the error with a more up-to-date version of CXF
2.4? If so, could you create a test-case that shows the problem and
attach it to a new JIRA?
Colm.
On Thu, Feb 16, 2012 at 1:08 PM, Nagamohan<[email protected]> wrote:
Hi Colm,
Thanks for your response
I have written a custom validator and registering it programatically with
following code
Map<String, Object> serviceProperties = new HashMap<String, Object>();
serviceProperties.put("ws-security.validate.token", "false");
serviceProperties.put("ws-security.ut.no-callbacks", "true");
serviceProperties.put("ws-security.ut.validator",
CustomUTValidator.class.getName());
endPoint.setProperties(serviceProperties);
With this it is still invoking UserNameTokenValidator instead of my custom
one.
Am i doing it in the right way?
Thanks,
-Nagamohan
--
View this message in context:
http://cxf.547215.n5.nabble.com/Apache-cxf-2-4-2-Custom-UserNameToken-validator-tp5489035p5489464.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
