Thanks Glen. Yes, i Tried to not mix wss4j and wss-policy, I configure wss4j properties just like This link you sent me, thats why I wonder if it really supports this certificate version. If I set only wss4j properties, I get an exception saying ''No signature Token'', so I put an empty SecurityToken in the requestContext and I see That my wss4j properties are read, but after I get a null pointer exception because the token dont have nothing inside.
If somebody knows some configuration should I take would be nice to know. Thanks! -----Mensagem original----- De: Glen Mazza [mailto:[email protected]] Enviada: terça-feira, 28 de agosto de 2012 15:21 Para: [email protected] Assunto: Re: Using cxf with X509v3 certificates The two articles here at link #14 might help: http://www.jroller.com/gmazza/entry/blog_article_index Make sure you're not mixing up the WSS4J and WS-SecurityPolicy methods, if you're using the latter don't configure like the former. Glen On 08/28/2012 01:20 PM, Nícolas Fontenele wrote: > > Hi all, > > I'm developing a client service to consume a .net service with x509v3 > certificate using ws-security. > > The Service uses symmetric binding, with > includeToken="prefix/AlwaysToRecipient" and a <sp:ProtectionToken>. > > I have two certificates, a *.pfx file and *.cer which I have to use to > access. > > My wsdl is attached. > > My question is Does cxf supports this configuration? > > Best Regards, > > *Nícolas Fontenele* >
