Hello,
Thanks for your reply, it got solved by using latest cxf jar.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Ws-SecurityPolicy-not-working-using-SOAP-UI-tp5729482p5729539.html
Sent from the cxf-user mailing list archive at Nabble.com.
;
> http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:ser="http://services.apachecxf.com/";>
>
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";>
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.
t;;>
joe
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";>Password
still it is not validated.
Please provide advise. HelloWorld.wsdl.xml
<http://cxf.547215.n5.nabble.com/file/n5729482/HelloWorl
Thanks - any way to avoid spnego by a client-side config?
Guy
On 19-mrt-2010, at 04:06, Daniel Kulp wrote:
On Thursday 18 March 2010 10:37:57 am Guy Pardon wrote:
> Hi,
>
> My case is the following: I would like to get ws-securitypolicy to work for
> signing messages with NTLM credentials on
On Thursday 18 March 2010 10:37:57 am Guy Pardon wrote:
> Hi,
>
> My case is the following: I would like to get ws-securitypolicy to work for
> signing messages with NTLM credentials on Java6.
Well, the work we did for Java6 just allows support of NTLM for http
authentication, not really for any
Hi,
My case is the following: I would like to get ws-securitypolicy to work for
signing messages with NTLM credentials on Java6.
Both of these would be supported by default (according to the cxf docs).
However, when I try our WSDL with the wsdl-first sample setup of cxf, then I
get the follo
