all groups > dotnet web services enhancements > june 2006 >
You're in the

dotnet web services enhancements

group:

WSE 3.0 usernameForCertificateSecurity doubt



WSE 3.0 usernameForCertificateSecurity doubt Jeffrey Sánchez
6/28/2006 9:26:53 AM
dotnet web services enhancements: 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.

RE: WSE 3.0 usernameForCertificateSecurity doubt lukezhan NO[at]SPAM online.microsoft.com
6/29/2006 12:00:00 AM
Hello Jeffrey,

I have to say this is impossible. The usernameForCertificateSecurity must
use X.509 certificates stored in CurrentUser or LocalMachine.

Regards,

Luke Zhang
Microsoft Online Community Lead

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
AddThis Social Bookmark Button