Re: Securing Webservice
- From: "Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 11 Dec 2006 22:11:57 -0600
The issue here is that your browser doesn't trust the certificate. IE isn't
installing a certificate when it gives you a warning, it is just telling you
it doesn't trust the certificate. In order to get the client to trust it,
you need to put the root certificate in the client's root certificate store.
Note that you'll need to do that for every client that will access the
server. If that is a lot of clients, you might want to consider a
certificate from a public CA. If they are all members of your domain, then
you can deploy an enterprise CA to get that root automatically installed on
each domain member.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"Bob" <bob@xxxxxxxxxxx> wrote in message
news:O$qmzYYHHHA.1240@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
I am new to web admin and security.
Made a certificate server out of the development Win2k server and created
a
root certificate.
The same machine is also the web server for now.
Updated the Web site directory properties to require SSL
When I query the site from a browser on the LAN it brings up the
certificate
question and the certificate install appears to go OK. The WSDL doc for my
service then appears
However if I start a new browser window it asks the certificate question
again.
Any clues as to where I am going wrong?
thanks
Bob
.
- Follow-Ups:
- Re: Securing Webservice
- From: Bob
- Re: Securing Webservice
- References:
- Securing Webservice
- From: Bob
- Securing Webservice
- Prev by Date: Securing Webservice
- Next by Date: Re: How to publish ASPNET web application locating the app files on shared folder
- Previous by thread: Securing Webservice
- Next by thread: Re: Securing Webservice
- Index(es):
Relevant Pages
|
|