This is a very common point of confusion - so you are not alone! :-)
You just need the web server certificate. We are using the Thawte 123 as it
meets our needs.
The web server cert will have a public and private key. You then install
that public key onto the user machines.
Note that when you install on the user machines, you need to be sure the
users install them into the correct store, becauseif you are deploying your
policy config files, that will have an explicit location identified in
there.
hth
Julie Lerman
> Hi
>
[quoted text clipped - 38 lines]
>
> Damian
Damian - 29 Mar 2006 16:34 GMT
Thank you so much! Finally someone who will give me a straight answer
:)
I have another question to follow. Something else that we need to do is
have 2 webservers communicate between each other using webservices. I
was thinking that I could use the x509 certificate options between the
2 servers.
We already have a Thawte Web Server Certificate on the one webserver.
Do we need to purchase another one for the webservices and one for the
other webserver, or can i use the existing web cert and just obtain
another cert for the other server?
Thanks very much
Damian
> This is a very common point of confusion - so you are not alone! :-)
>
[quoted text clipped - 55 lines]
> >
> > Damian
Mark - 13 Apr 2006 22:31 GMT
How do you install the public server key onto the client? Do you create a
cert from the server cert?
Brian Smith - 20 Apr 2006 19:17 GMT
Hah, I at least know that - using the mmc snap-in on the server, you
Export the Certificate to a file. The export wizard has an option to
only export the public key.
What I don't know is if its possible to install the certificate on the
client as part of the client installation process. (I'm hoping to use
ClickOnce)
brian smith
> How do you install the public server key onto the client? Do you create a
> cert from the server cert?