Re: invalid certificate
- From: "Brian Komar" <brian.komar@xxxxxxxxxxxxxxxxx>
- Date: Sun, 12 Aug 2007 09:19:06 -0500
Look at the Best Practices whitepaper available at www.microsoft.com/pki.
You need to designate your root CA as a trusted root for all clients. I assume that client's are connecting from their home computers, etc. In this case, you should have used a certificate that chained to a commercial root CA.
The best purpose for internal CAs is for WEb sites that are *only* connected to by internally managed clients.
Brian
"tree leafs" <treeleafs@xxxxxxxxxxx> wrote in message news:%23ryKhAM3HHA.5360@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have just installed windows certificate service and selected an enterprisse root ca. I then issued a certificate to the default website for enabling OWA over HTTPS. All seemed OK, but when users connect to the OWA site the certificate cannot be installed into the trusted root CA. When viewing the certificate, it says "This certificate cannot be verified up to a trusted certificate authority". Is this normal for windows CA? or there is something wrong in installing the CA and creating the certificate?
Thanks in advance,
.
- References:
- invalid certificate
- From: tree leafs
- invalid certificate
- Prev by Date: invalid certificate
- Next by Date: log off script that prevents loggoff if user has app open
- Previous by thread: invalid certificate
- Next by thread: log off script that prevents loggoff if user has app open
- Index(es):
Relevant Pages
|