AmilaJ, I am using Rampart 1.5.1 and I do have a password call-back class. I am also using the same policy as used in sample 05 of the distribution which uses the AsymmetricBinding. When I created a new policy using a TransportBinding, I get a usernametoken in the header but it does not sign it.
Thanks, Scott On Thu, May 19, 2011 at 10:02 PM, Amila Jayasekara <[email protected]> wrote: > Hi Scott, > Just wanted to confirm whether you specified a password call-back > class in your rampart configuration. > Also what is the rampart version you are using ? > > Thanks > AmilaJ > > > > On Wed, May 18, 2011 at 7:23 PM, Scott B <[email protected]> wrote: > > I am trying to get the rampart sts policy sample 05 to use a > usernametoken > > and I have added the following in my sts_policy.xml file > > > > <sp:SignedSupportingTokens wsp:Usage="wsp:Required" > > xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";> > > <wsp:Policy> > > <sp:UsernameToken > > sp:IncludeToken=" > http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient > " > > /> > > </wsp:Policy> > > </sp:SignedSupportingTokens> > > > > When I run the client, I do not see any usernametoken in the soap message > > going to the sts. > > > > Please help! > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
