Hi,
After readfing the Web Security Guide, I tried to implement ditrect
authentication using a UsernameToken by implementing the
usernameForCertificateSecurity policy.
I have a web application client which communicates with a service. I have a
login page where the client need to provides it's credentials.
My question is - should I use the usernameForCertificateSecurity policy all
over my web application when calling the service?
I want to maintain the authetication of the client who's calling the
service, and if I understood correctly, when using
usernameForCertificateSecurity, I authenticate the client using it's
credentials and after I authethenticate the client, a derieved key is created
and each call to the service is authenticated using this derived key.
Thanks
Yoav
Pablo Cibraro - 30 Mar 2006 20:02 GMT
Hi YC,
That depends on the secureConversation setting.
If the secureConversation flag is turned on in your UsernameForCertificate
assertion, it will work as you said,
the client is authenticated only the first time and then a session key is
used. (As long, you use the same proxy instance).
If you create a new proxy instance each time or secureConversation is turned
off, then the user client will be authenticated for each message.
Does this anwser your question ?.
Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
> Hi,
>
[quoted text clipped - 18 lines]
>
> Yoav
YC - 02 Apr 2006 08:51 GMT
Hi,
thanks for your reply.
I don't exactly understand this process in full.
I'll look into it.
Thanks
Yoav
> Hi YC,
>
[quoted text clipped - 34 lines]
> >
> > Yoav
Pablo Cibraro - 03 Apr 2006 20:33 GMT
Hi YC,
You can find an article about this topic in my blog,
http://weblogs.asp.net/cibrax/archive/2006/02/21/438670.aspx
Regards,
Pablo Cibraro.
> Hi,
> thanks for your reply.
[quoted text clipped - 46 lines]
>> >
>> > Yoav
YC - 04 Apr 2006 07:51 GMT
Thanks Pablo,
I'll look into it.
Yoav
> Hi YC,
>
[quoted text clipped - 55 lines]
> >> >
> >> > Yoav