> How can I define a policy that would sign and/or encrypt with a kerberos
> token or a usernametoken (I am assuming you can sign with a usernametoken, I
[quoted text clipped - 16 lines]
> Thanks in advance,
> Indra
Check the QuickStart samples for the product: each sample has a code
variant and a policy variant, the UsernameToken signing example should
have what you need.

Signature
This posting is provided "AS IS", with no warranties, and confers no rights.
IP - 27 Sep 2004 23:49 GMT
The sample just shows signing with the username token. I take it that the
username token can also be used to somehow encrypt the message also.
Is there some place where I can find details of how the username is used to
sign and encrypt the message. I would like to understand the mechanism.
I take it that the password is no longer in plain text in a message that is
signed and encrypted with the username token ... because if it is not, can't
someone sniff the password and replace the signed encrypted message with one
of their own?
Thanks again,
IP
> > How can I define a policy that would sign and/or encrypt with a kerberos
> > token or a usernametoken (I am assuming you can sign with a usernametoken, I
[quoted text clipped - 20 lines]
> variant and a policy variant, the UsernameToken signing example should
> have what you need.
Hervey Wilson [MSFT] - 28 Sep 2004 06:27 GMT
> The sample just shows signing with the username token. I take it that the
> username token can also be used to somehow encrypt the message also.
[quoted text clipped - 34 lines]
>>variant and a policy variant, the UsernameToken signing example should
>>have what you need.
You should not use the UsernameToken to both sign and encrypt a message
to a service; instead you should sign with the username token and then
encrypt the token and the message using the services token. If you don't
have the services token, you should strongly consider sending this
initial message over a secure channel (always a good thing w/ the
UsernameToken).
The response from the service can be encrypted with the clients signing
token by marking the signing token in policy as the identity token. This
should be illustrated in the ResponseEncryption sample.

Signature
This posting is provided "AS IS", with no warranties, and confers no rights.