WSE 3.0 usernameForCertificateSecurity doubt
- From: "Jeffrey Sánchez" <jsanchez@xxxxxxxxxxxxxxxxx>
- Date: Wed, 28 Jun 2006 09:26:53 -0600
Hi.
I'm developing a winform app that communicates with a secure web service
using WSE 3.0. I'm trying to implement Direct Authentication with
UsernameToken. I'm also trying to establish the message integrity using
usernameForCertificateSecurity turnkey security.
One fact is that I don't want my client to install any X.509 certificate.
Does the use of usernameForCertificateSecurity element means that the client
MUST have a X.509 certificate installed?
Is there a way to go without the client having to install any certificate
and still use the usernameForCertificateSecurity element or in that case the
only way to go is to use usernameOverTransportSecurity over HTTPS?
Thanks for your answer.
.
- Follow-Ups:
- RE: WSE 3.0 usernameForCertificateSecurity doubt
- From: Luke Zhang [MSFT]
- RE: WSE 3.0 usernameForCertificateSecurity doubt
- Prev by Date: ASP.NET Development Server
- Next by Date: Re: WSE 3.0, usernameOverTransportSecurity, custom Token Manager w/ securityTokenManager,
- Previous by thread: ASP.NET Development Server
- Next by thread: RE: WSE 3.0 usernameForCertificateSecurity doubt
- Index(es):
Relevant Pages
|
|