Re: Securing Webservice
- From: "Bob" <bob@xxxxxxxxxxx>
- Date: Fri, 15 Dec 2006 10:16:21 +1300
Hi Joe,
Thanks for your help.
I should now be able to sort it out.
(Famous last words)
I can't look at it at present but will post back when I have a result.
regards
Bob
"Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eF7eTE0HHHA.3268@xxxxxxxxxxxxxxxxxxxxxxx
This is all much easier if you get a certificate from a public CA as theyone
typically have their CA certs already installed in the trusted roots cert
store in Windows, so you won't have trust issues. That said, lots of
companies have their own internal CAs with roots that don't chain up to
of the standard root CAs, and they get this to work by installing theirroot
certificate in the appropriate Windows store. Generally, this is donein
through some mechanism like group policy or something.
It sounds like your certificate's CA cert has not actually been installed
your machine's trusted root store, despite the fact that you have alreadyneed
tried to do that. Otherwise, you wouldn't be getting a cert trust error.
If the certificate is self-signed (not issued by another CA), then you
to put the cert itself in the trusted root store. If not, then you needto
put the root certificate for the entire cert chain (however many CAs thatProgramming"
is) in the trusted root store.
Unfortunately, I can't see your machine, so whatever isn't working isn't
obvious to me or we could probably fix this easily. :(
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
http://www.directoryprogramming.netI
--
"Bob" <bob@xxxxxxxxxxx> wrote in message
news:OwUWORyHHHA.3952@xxxxxxxxxxxxxxxxxxxxxxx
Hi Joe,
The only thing in the Certification path is my development machine which
aset up as the one and only certificate server in our company.
The information message says "This certificate cannot be verified up to
mytrusted certification authority"
Is it inferring that basically my machine needs to be authorised by a
higher
level.
In other words do I need to engage a commercial third party to verify
iscertificates?
i.e. Issuing your own certificates based entirely on your own authority
thenot good enough?
Thanks
Bob
"Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:O%23PdWXnHHHA.3780@xxxxxxxxxxxxxxxxxxxxxxx
Ok, if it is a trust issue, then when you open up the certificate in
seecertificates UI and switch to the Certification Path tab, you should
securitywhere the trust chain is being broken. That should tell you what ismissing
or is not being trusted properly.Programming"
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
http://www.directoryprogramming.netsecurity
--
"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
certificate.
Then there is an information icon alongside which it says 'The
Viewcertificate was issued by a company you have not chosen to trust.
pagethe
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
someyou
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
certificateexpiration.other
cert problem such as a cert name/URL host mismatch or a cert
What exactly does the cert warning dialog say?Programming"
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
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
goon
the
client successfully.
When the browser brings up the Certificate question dialog box I
proceeddown
the
view certificate -> install certificate path. This seems to
certificatecorrectly.
I have tried letting the wizard choose where to put the
awayas
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
towe
machines.go
again.
The goal is to deploy a thick client on a couple of external
beenthe
My test Http deployment went OK. but now I have clamped down to
Https
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
told
to trust any certificate. Still, it is a starting point to trying
certificate.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
accessIE
trusttellingisn't
installing a certificate when it gives you a warning, it is just
you
it doesn't trust the certificate. In order to get the client to
certificateit,
you need to put the root certificate in the client's root
store.
Note that you'll need to do that for every client that will
athe
server. If that is a lot of clients, you might want to consider
anddomain,certificate from a public CA. If they are all members of your
installedthen
you can deploy an enterprise CA to get that root automatically
on
each domain member.Programming"
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
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
thecreated
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
doccertificate
question and the certificate install appears to go OK. The WSDL
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
.
- References:
- Securing Webservice
- From: Bob
- Re: Securing Webservice
- From: Joe Kaplan
- Re: Securing Webservice
- From: Bob
- Re: Securing Webservice
- From: Joe Kaplan
- Re: Securing Webservice
- From: Bob
- Re: Securing Webservice
- From: Joe Kaplan
- Re: Securing Webservice
- From: Bob
- Re: Securing Webservice
- From: Joe Kaplan
- Securing Webservice
- Prev by Date: Re: ASP.Net security problem after publishing
- Next by Date: RE: "correct" way to encrypt a connection string
- Previous by thread: Re: Securing Webservice
- Next by thread: Re: Securing Webservice
- Index(es):
Relevant Pages
|