Contents
When a crawler requests a connection to crawl a site, the system generates a warning if there is a problem with the site’s SSL certificate. By default, the crawler does not crawl the site when this happens. For security reasons, we strongly recommend that you do not change this default crawler behavior unless you have sufficient reason to do so.
Tap or click Start, type mmc in Start search, and then press Enter. On the File menu, click Add/Remove Snap-in. Under Available snap-ins, click Certificates, and then click Add. Under This snap-in will always manage certificates for, select Computer account, and then click Next.
How to track a certificate validation failure in SharePoint?
Certificate validation failures can be tracked by enabling the CAPI2 event logging on the SharePoint server. When CAPI2 event logging is enabled and Internet certificate validation is failing, you will frequently see the following error messages in the CAPI2 event log:
By default, the root certificate in the chain is not added to the Trusted Root Certificate Authorities store of the SharePoint servers. Because of this, the certificate revocation list (CRL) check for the certificate is performed over the Internet.
Is there a troubleshooting document for client certificates?
Client Certificates troubleshooting will not be covered in this document. Server Certificates are meant for Server Authentication and we will be dealing only with Server Certificates in this document. If the Client certificates section is set to “Require” and then you run into issues, then please don’t refer this document.
Are there any warranties on Microsoft SSL certificates?
Microsoft makes no warranties, express or implied. This document will help you in troubleshooting SSL issues related to IIS only. Client Certificates troubleshooting will not be covered in this document. Server Certificates are meant for Server Authentication and we will be dealing only with Server Certificates in this document.
You have a custom solution that authenticates with SharePoint Online. Your solution is coded to exclusively use the GTE CyberTrust Global Root certificate. When you try to use the solution, authentication doesn’t finish. You’re using an operating system and browser combination that doesn’t have the Baltimore CyberTrust Root certificate installed.