Re: Securing Webservice

Ok, if it is a trust issue, then when you open up the certificate in the
certificates UI and switch to the Certification Path tab, you should see
where the trust chain is being broken. That should tell you what is missing
or is not being trusted properly.

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:ewXS$9lHHHA.420@xxxxxxxxxxxxxxxxxxxxxxx
Hi Joe,
Thanks for following up.
It looks like trust to me.
It has a 'Security Alert ' dialog box.
In summary the dialog box says there is a problem with the sites security
certificate.

Then there is an information icon alongside which it says 'The security
certificate was issued by a company you have not chosen to trust. View the
certificate to determine whether you want to trust the certifying
authority."
This is followed by two green tick icons stating:
1) that the certificate date is valid.
2) "the certificate has a valid name matching the the name of the page you
are trying to view"
regards
Bob
"Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eRxOlJjHHHA.420@xxxxxxxxxxxxxxxxxxxxxxx
Perhaps the issue isn't with a certificate trust issue, but with some
other
cert problem such as a cert name/URL host mismatch or a cert expiration.
What exactly does the cert warning dialog say?

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:OA7Fd3iHHHA.4112@xxxxxxxxxxxxxxxxxxxxxxx
Hi Joe,
Thanks for your reply.

The problem apppears to be that I am not installing the certificate on
the
client successfully.
When the browser brings up the Certificate question dialog box I go
down
the
view certificate -> install certificate path. This seems to proceed
correctly.
I have tried letting the wizard choose where to put the certificate as
well
as taking the manual path and selecting Trusted Root Certicate Store.
In
both cases I am told the import is successful.

However a new browser window gets the certificate question and away we
go
again.

The goal is to deploy a thick client on a couple of external machines.

My test Http deployment went OK. but now I have clamped down to Https
the
newly installed test app errors trying to connect.

I am assuming that the inability of the browser to repeatedly use the
certificate is related but this may not be correct as the app has been
told
to trust any certificate. Still, it is a starting point to trying to
figure
out what is wrong.

Thanks
Bob

"Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:uooZrOaHHHA.420@xxxxxxxxxxxxxxxxxxxxxxx
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












.

Relevant Pages

  • Re: Securing Webservice
    ... is) in the trusted root store. ... Joe Kaplan-MS MVP Directory Services Programming ... Co-author of "The .NET Developer's Guide to Directory Services ... The information message says "This certificate cannot be verified up to ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Proposal for a new PKI model (At least I hope its new)
    ... That is say I trust Paul Rubin's public key. ... two basic reasons for the SSL server domain name certificate: ... certificates have to check with the domain name infrastructure to see ... CA/PKI industry is that public keys be registered with the domain name ...
    (sci.crypt)
  • Re: How do I store secrets?
    ... One of the aspects of digital signature verification that is too often ... since encrypted with the PRIVATE key for which you have, and TRUST, ... If the certificate is issued by a KNOWN and TRUSTED CA, ... Then you create a server ...
    (microsoft.public.dotnet.security)
  • Re: New Method for Authenticated Public Key Exchange without Digital Certificates
    ... you are referring to any situation where there might be some trust ... resorting again to the merged security taxonomy and glossary ... as definitions specifically within the context of a Public Key, ... Certificate, Certification Authority environment. ...
    (sci.crypt)
  • Re: verisign security,lol
    ... "Igor Tandetnik" wrote: ... In order to provide this trust, ... > certificate, and keeps the company's vital stats on file. ... Dont believe average user cares what ca is used anyways. ...
    (microsoft.public.vc.atl)