06-29-05 07:48 AM
SelfSSL should set up your IIS machine to handle client cert authentication.
http://www.microsoft.com/downloads/...&DisplayLang=en
To get rid of the security popup of the browser, you will need to sign with
a certificate that the client trusts. This is accomplished by either
purchasing a SSL Certificate (verisign, thawte, et al have their
certificates in the client's trusted store), or you somehow the server's
cert into the client's trusted store.
Obviously, for testing purposes, SelfSSL + manual registration of the cert
into the client's trusted store is the cheap way to go. For real deployment,
real signed certificate is the easy way to go (unless you control all the
client browsers and can deploy your self-signed cert into their trusted
store).
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Marc Jennings" <MarcJennings@community.nospam> wrote in message
news:01i2c1hjhgcmo2roktgn97hdphodgefhjo@
4ax.com...
Hi there,
Can anyone give me a quick tutorial on creating a self-signed client
certificate in win2K3 / IIS6, please? I have just been handed a
project with a dealine of uesterday that requires client certificate
authentication. Any help is greatfully accepted.
TIA
Marc.
[ Post a follow-up to this message ]
| 
