
Signature
------------------------
Pravin Patil
Hi Pravin,
The secure context feature is a better way of implementing that.
It was designed to avoid sending the username token everytime. This feature
works as I will describe below:
1. The client sends the username token to the service, and they negotiate a
secure context session.
2. The client receives a secure contex token from the service, which can be
used to protect the communication during that session.
You can enable this feature setting the "establishSecurityContext" attribute
to true.
<usernameForCertificateSecurity establishSecurityContext="true" .....>
Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
http://www.lagash.com
> Hi,
>
[quoted text clipped - 13 lines]
>
> Pravin Patil
Pravin Patil - 14 Nov 2005 15:36 GMT
Thanks for quick response, Pablo.
Can you please suggest me a few sample/link where it has been implemented or
explained?
------------------------
Pravin Patil
> Hi Pravin,
> The secure context feature is a better way of implementing that.
[quoted text clipped - 33 lines]
> >
> > Pravin Patil
Pablo Cibraro - 14 Nov 2005 20:32 GMT
Sure, you can find a good sample in the WSE quickstarts.
[WSE Installation
folder]\v3.0\Samples\CS\QuickStart\Security\SecureConversation
Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
http://www.lagash.com
> Thanks for quick response, Pablo.
> Can you please suggest me a few sample/link where it has been implemented
[quoted text clipped - 46 lines]
>> >
>> > Pravin Patil