You should try something along those lines:

  <http:policies>
    <soap:ws-security sendAction="UsernameToken" username="smx" />
  </http:policies>

Cheers,
Guillaume Nodet

On 8/6/07, Simon Sekat <[EMAIL PROTECTED]> wrote:
> My question still stands.  Could anyone give direction on developing a HTTP
> provider endpoint invoking web services that use WS UsernameToken?
>
> Thanks.
>
> On 8/3/07, Simon Sekat <[EMAIL PROTECTED]> wrote:
> >
> > I was asking for HTTP provider endpoint.
> >
> > But I thank you for your suggestion about http consumer.  Would you have
> > any HTTP consumer examples that I can learn from.  Thank you.
> >
> > On 8/3/07, netflexity <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > > I've done it before by adding http policy to http consumer:
> > >
> > > <http:policies>
> > >         <soap:ws-security receiveAction="NoSecurity UsernameToken"/>
> > > </http:policies>
> > >
> > >
> > > Simon Sekat wrote:
> > > >
> > > > I'd like to invoke an external web service that requires WS
> > > UsernameToken
> > > > header.  The following is an example request that carries username,
> > > nonce,
> > > > digested password, created timestamp to the service.
> > > >
> > > > http://incubator.apache.org/servicemix/ws-security.html talked about
> > > how a
> > > > HTTP consumer endpoint uses WS UsernameToken.  Can someone enlighten
> > > me
> > > > how
> > > > to develop a HTTP provider endpoint using WS UsernameToken?  Thank
> > > you.
> > > >
> > > >     <?xml version="1.0" encoding="UTF-8"?>
> > > >>     <soapenv:Envelope
> > > >>         xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/";
> > > >>         xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > > >>         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> > > >>         <soapenv:Header>
> > > >>             <wsse:Security
> > > >>
> > > >> soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next";
> > > >>                 soapenv:mustUnderstand="1"
> > > >>                 xmlns:wsse="
> > > >>
> > > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> > > >> ">
> > > >>                 <wsse:UsernameToken wsu:Id="LOGIN"
> > > >>                     xmlns:wsu="
> > > >> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
> > >
> > > >> ">
> > > >>                     <wsse:Username>admin</wsse:Username>
> > > >>                     <wsse:Password
> > > >>                         Type="
> > > >>
> > > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest
> > > >> ">
> > > >>                         eDQUHeku0Mr188gx8Eo88Ik1tK8=
> > > >>                     </wsse:Password>
> > > >>                     <wsse:Nonce>MTE4NjA4NDcyNDYxMA==</wsse:Nonce>
> > > >>                     <wsu:Created>2007-08-02T19:58:44Z</wsu:Created>
> > > >>                 </wsse:UsernameToken>
> > > >>             </wsse:Security>
> > > >>         </soapenv:Header>
> > > >>         <soapenv:Body>
> > > >>             <Login
> > > >>                 xmlns=" http://testserver.com/test1/TWebService/Login
> > > ">
> > > >>                 <userLoginId>admin</userLoginId>
> > > >>             </Login>
> > > >>         </soapenv:Body>
> > > >>     </soapenv:Envelope>
> > > >>
> > > >
> > > > --
> > > >
> > > > Simon S.
> > > >
> > > >
> > >
> > > --
> > > View this message in context:
> > > http://www.nabble.com/How-can-I-develop-a-HTTP-provider-endpoint-invoking-web-services-that-use-WS-UsernameToken--tf4212467s12049.html#a11989341
> > > Sent from the ServiceMix - User mailing list archive at Nabble.com.
> > >
> > >
> >
> >
> > --
> >
> > Simon S.
>
>
>
>
> --
>
> Simon S.
>


-- 
Cheers,
Guillaume Nodet
------------------------
Principal Engineer, IONA
Blog: http://gnodet.blogspot.com/

Reply via email to