Details of the event with ID 21 of the source Microsoft-Windows-Kerberos-Key-Distribution-Center

Event Source:Microsoft-Windows-Kerberos-Key-Distribution-Center
Event ID:21 (0x80000015)
Event log:System
Event type:Warning
Event text (English):The client certificate for the user %1\%2 is not valid, and resulted in a failed smartcard logon. Please contact the user for more information about the certificate they're attempting to use for smartcard logon. The chain status was : %3
Event text (German):Das Clientzertifikat für den Benutzer %1\%2 ist nicht gültig. Das Ergebnis war ein Fehler bei der Smartcard-Anmeldung. Wenden Sie sich an den Benutzer, um weitere Informationen über das Zertifikat zu erhalten, das für die Smartcard-Anwendung verwendet werden soll. Kettenstatus: %3

Do you know TameMyCerts? TameMyCerts is an add-on for the Microsoft certification authority (Active Directory Certificate Services). It extends the function of the certification authority and enables the application of rule sets to realize the secure automation of certificate issuance. TameMyCerts is unique in the Microsoft ecosystem, has already proven itself in countless companies around the world and is available under a free license. It can be downloaded via GitHub and used free of charge. Professional maintenance is also offered.

Parameter

The parameters contained in the event text are filled with the following fields:

  • %1: Domain (win:UnicodeString)
  • %2: Username (win:UnicodeString)
  • %3: Status (win:UnicodeString)
  • %4: __binLength (win:UInt32)
  • %5: binary (win:Binary)

Example events

The client certificate for the user INTRA\Administrator is not valid, and resulted in a failed smartcard logon. Please contact the user for more information about the certificate they're attempting to use for smartcard logon. The chain status was : The revocation function was unable to check revocation because the revocation server was offline.

Event 21, Kerberos-Key-Distribution-Center: failed smartcard logon, chain status "The revocation function was unable to check revocation because the revocation server was offline."

The client certificate for the user INTRA\Administrator is not valid, and resulted in a failed smartcard logon. Please contact the user for more information about the certificate they're attempting to use for smartcard logon. The chain status was : The operation completed successfully.

Event 21, Kerberos-Key-Distribution-Center: failed smartcard logon, chain status "The operation completed successfully."

The client certificate for the user INTRA\Administrator is not valid, and resulted in a failed smartcard logon. Please contact the user for more information about the certificate they're attempting to use for smartcard logon. The chain status was : The certificate is not valid for the requested usage.

Event 21, Kerberos-Key-Distribution-Center: failed smartcard logon, chain status "The certificate is not valid for the requested usage."

The client certificate for the user INTRA\Administrator is not valid, and resulted in a failed smartcard logon. Please contact the user for more information about the certificate they're attempting to use for smartcard logon. The chain status was : A certification chain processed correctly, but one of the CA certificates is not trusted by the policy provider.

Event 21, Kerberos-Key-Distribution-Center: failed smartcard logon, a CA certificate is not trusted by the policy provider

Description

The revocation function was unable to check revocation because the revocation server was offline.

Occurs when there are problems with the revocation infrastructure.

Also occurs when domain controllers are hard-configured to use OCSP , the Online Responders (OCSP) are configured for a deterministic good and the returned status is "Unknown".

In this case, both events should be correlated.

Event 5125, Microsoft Windows security auditing: "A request was submitted to OCSP Responder Service.", Revocation Status Unknown (marked)

See also article "Details of the event with ID 5125 of the source Microsoft-Windows-Security-Auditing ".

The operation completed successfully.

Occurs when a PKINIT is attempted but the name in the Subject Alternative Name (SAN) does not match for the requested user (KDC_ERR_CLIENT_NAME_MISMATCH).

The certificate is not valid for the requested usage.

Occurs when a PKINIT is attempted with a certificate that contains the Extended Key Usage (EKU) neither for "Client Authentication" nor for "Smartcard Logon".

A certification chain processed correctly, but one of the CA certificates is not trusted by the policy provider.

Occurs when a smart card logon is performed with a certificate from a certification authority that is not listed in the NTAuthCertificates object in Active Directory.

Security assessment

The security assessment is based on the three dimensions of confidentiality, integrity and availability.

If the event occurs due to incorrect revocation information, the availability is affected and the event is rated as critical.

If the event occurs due to an "Unknown" status returned by the Online Responder, this may indicate the use of a compromised certificate. In this case, too, the event must be rated as "critical".

The same applies in the event that a logon is attempted with a certificate whose issuing certification authority is not located in the NTAuthCertificates object in Active Directory.

External sources