Article ID: 2802568 - View products that this article applies to.
Consider the following scenario. You have an Internet Information Services (IIS) 8 web application that is configured to use SSL and client certificate authentication. You install a certificate that is not self-signed, such as an Intermediate CA certificate, into the Local Computer --> Trusted Root Certification Authorities certificate store on the IIS server. When a user then sends an HTTP request to the web application and attempts to authenticate using a client certificate, one of the following error messages may be sent as a response by the IIS server:
HTTP 403.16 - Client certificate is untrusted or invalid.
HTTP 403.7 - Client certificate required.
The problem's symptoms may vary depending on the configuration and use of a Certificate Trust List (CTL) on the IIS server:
SCENARIO 1 - HTTP 403.16 error
If IIS is not configured to use a CTL, SSL client certificate authentication will fail with the 403.16 error condition. This error occurs because SChannel.dll wrongly considers the client certificate to be untrusted. (NOTE: Having no CTL in use is the default configuration of IIS 8.0. This is configured by having no SendTrustedIssuerList present or by setting SendTrustedIssuerList=0).
In this scenario, the IIS log typically shows a value of 2148204809 in the sc-win32-status field. This translates to error code 0x800b0109, which is defined as CERT_E_UNTRUSTEDROOT.
SCENARIO 2 - HTTP 403.7 error
If IIS is configured to use a CTL (SendTrustedIssuerList=1), client certificate authentication fails with the 403.7 error condition. This error occurs because the CTL sent by IIS does not contain the Trusted Root Certificate for the user's client certificate, therefore Internet Explorer is not able to present the user with any valid client certificates to choose from.
To workaround these issues, uninstall the non-self-signed certificate from the Local Computer --> Trusted root Certification authorities certificate store on the IIS server.
This issue has the same root cause as the problem described in the following article that effects Lync Server :
You may consider using the powershell script provided in the above article to detect the non-self-signed certificates installed in the Trusted Root Certification Authorities certificate store.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2802568 - Last Review: January 25, 2013 - Revision: 6.0