Event Source: | Microsoft-Windows-OnlineResponderWebProxy |
Event ID: | 19 (0x13) |
Event log: | Application |
Event type: | Information |
Event text (English): | The Online Responder web proxy is unloaded. |
Event text (German): | The online responder web proxy is unloaded. |
Details of the event with ID 18 of the source Microsoft-Windows-OnlineResponderWebProxy
Event Source: | Microsoft-Windows-OnlineResponderWebProxy |
Event ID: | 18 (0x12) |
Event log: | Application |
Event type: | Information |
Symbolic Name: | MSG_E_MISMATCHED_BASE_DELTA_CRL |
Event text (English): | The Online Responder web proxy is successfully loaded. |
Event text (German): | The online responder web proxy was loaded successfully. |
Details of the event with ID 17 of the source Microsoft-Windows-OnlineResponderWebProxy
Event Source: | Microsoft-Windows-OnlineResponderWebProxy |
Event ID: | 17 (0x11) |
Event log: | Application |
Event type: | Error |
Symbolic Name: | MSG_E_INVALID_CRL |
Event text (English): | The Online Responder web proxy failed to Initialize. %1 |
Event text (German): | The online responder web proxy could not be initialized. %1 |
Details of the event with ID 32 of the source Microsoft-Windows-Kerberos-Key-Distribution-Center
Event Source: | Microsoft Windows Kerberos Key Distribution Center |
Event ID: | 32 (0x80000020) |
Event log: | System |
Event type: | Warning |
Event text (English): | The Key Distribution Center (KDC) uses a certificate without KDC Extended Key Usage (EKU) which can result in authentication failures for device certificate logon and smart card logon from non-domain-joined devices. Enrollment of a KDC certificate with KDC EKU (Kerberos Authentication template) is required to remove this warning. |
Event text (German): | The Key Distribution Center (KDC) uses a certificate without Extended Key Usage (EKU) for the KDC. This can lead to authentication errors during device certificate enrollments and smart card enrollments of devices without domain affiliation. Enrollment of a KDC certificate with KDC EKU (Kerberos authentication template) is required to eliminate this warning. |
Details of the event with ID 200 of the source Microsoft-Windows-Kerberos-Key-Distribution-Center
Event Source: | Microsoft Windows Kerberos Key Distribution Center |
Event ID: | 200 (0xC8) |
Event log: | Microsoft-Windows-Kerberos-Key-Distribution-Center/Operational |
Event type: | Warning |
Event text (English): | The Key Distribution Center (KDC) cannot find a suitable certificate to use. This KDC is not enabled for smart card or certificate authentication. |
Event text (German): | The Key Distribution Center (KDC) cannot find a suitable certificate. This KDC is not enabled for smart card or certificate authentication. |
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): | The client certificate for user %1\%2 is not valid. The result was an error during smartcard login. Contact the user for more information about the certificate to be used for the smartcard application. Chain status: %3 |
Details of the event with ID 302 of the source Microsoft-Windows-Kerberos-Key-Distribution-Center
Event Source: | Microsoft Windows Kerberos Key Distribution Center |
Event ID: | 302 (0x12E) |
Event log: | Microsoft-Windows-Kerberos-Key-Distribution-Center/Operational |
Event type: | Information |
Event text (English): | The Key Distribution Center (KDC) uses the below KDC certificate for smart card or certificate authentication. Kdc Certificate Information: Issuer Name: %1 Serial Number: %2 Thumbprint: %3 Template: %4 |
Event text (German): | The Key Distribution Center (KDC) uses the following certificate for smart card or certificate authentication. KDC certificate information: Issuer name: %1 Serial number: %2 Fingerprint: %3 Template: %4 |
Details of the event with ID 19 of the source Microsoft-Windows-Kerberos-Key-Distribution-Center
Event Source: | Microsoft Windows Kerberos Key Distribution Center |
Event ID: | 19 (0x80000013) |
Event log: | System |
Event type: | Warning |
Event text (English): | This event indicates an attempt was made to use smartcard logon, but the KDC is unable to use the PKINIT protocol because it is missing a suitable certificate. |
Event text (German): | This event indicates that an attempt was made to use the smart card login, but the KDC cannot use the PKINIT protocol because a suitable certificate is missing. |
Details of the event with ID 20 of the source Microsoft-Windows-Kerberos-Key-Distribution-Center
Event Source: | Microsoft Windows Kerberos Key Distribution Center |
Event ID: | 20 (0x80000014) |
Event log: | System |
Event type: | Warning |
Event text (English): | The currently selected KDC certificate was once valid, but now is invalid and no suitable replacement was found. Smartcard logon may not function correctly if this problem is not remedied. Have the system administrator check on the state of the domain's public key infrastructure. The chain status is in the error data. |
Event text (German): | The currently selected KDC certificate was previously valid but is now invalid. No suitable replacement has been found. Smart card logon may not work properly if this issue is not resolved. Have the system administrator check the status of the domain's public key infrastructure (PKI). The chain status is included in the error data. |
Details of the event with ID 29 of the source Microsoft-Windows-Kerberos-Key-Distribution-Center
Event Source: | Microsoft Windows Kerberos Key Distribution Center |
Event ID: | 29 (0x8000001D) |
Event log: | System |
Event type: | Warning |
Event text (English): | The Key Distribution Center (KDC) cannot find a suitable certificate to use for smart card logons, or the KDC certificate could not be verified. Smart card logon may not function correctly if this problem is not resolved. To correct this problem, either verify the existing KDC certificate using certutil.exe or enroll for a new KDC certificate. |
Event text (German): | The Key Distribution Center (KDC) cannot find a suitable certificate for smart card logins, or the KDC certificate could not be verified. Smart card logins may not work properly until this issue is resolved. To resolve this issue, either verify the existing KDC certificate using certutil.exe, or register for a new KDC certificate. |
Details of the event with ID 120 of the source Microsoft-Windows-Kerberos-Key-Distribution-Center
Event Source: | Microsoft Windows Kerberos Key Distribution Center |
Event ID: | 120 (0x78) |
Event log: | Microsoft-Windows-Kerberos-Key-Distribution-Center/Operational |
Event type: | Error |
Event text (English): | The Key Distribution Center (KDC) failed to validate its current KDC certificate. This KDC might not be enabled for smart card or certificate authentication. Kdc Certificate Information: Issuer Name: %1 Serial Number: %2 Thumbprint: %3 Template: %4 Kerberos Error: %5 Validation Error: %6 |
Event text (German): | The Key Distribution Center (KDC) could not verify the current KDC certificate. This KDC may not be able to be used for smart card or certificate authentication. KDC certificate information: Issuer name: %1 Serial number: %2 Fingerprint: %3 Template: %4 Kerberos error: %5 Verification error: %6 |
Change the signing algorithm of a certification authority hierarchy without issuing new certification authority certificates
Sometimes it may be necessary to change the Signature algorithm to subsequently change an already installed certification authority hierarchy.
This is often the case because one has installed them with PKCS#1 version 2.1 and unfortunately finds out afterwards that not all applications are compatible with the resulting certificates, and thus cannot use the hierarchy.
While it is relatively easy to change the signature algorithm for certificates issued by a certification authority, it is more difficult to do so for certification authority certificates.
Continue reading „Den Signaturalgorithmus einer Zertifizierungsstellen-Hierarchie ändern, ohne neue Zertifizierungsstellen-Zertifikate auszustellen“The certification authority service does not start and throws the error message "The parameter is incorrect. 0x80070057 (WIN32: 87 ERROR_INVALID_PARAMETER)".
Assume the following scenario:
- A certification authority is implemented in the network.
- The certification authority service does not start.
- When trying to start the Certification Authority service, you get the following error message:
The parameter is incorrect. 0x57 (WIN32: 87 ERROR_INVALID_PARAMETER)Continue reading „Der Zertifizierungsstellen-Dienst startet nicht und wirft die Fehlermeldung „The parameter is incorrect. 0x80070057 (WIN32: 87 ERROR_INVALID_PARAMETER)““
Configuring PKCS#1 Version 2.1 for Issued Certificates and Revocation Lists of a Certification Authority
Sometimes it may be necessary to change the Signature algorithm of an already installed certification authority subsequently.
Continue reading „PKCS#1 Version 2.1 für ausgestellte Zertifikate und Sperrlisten einer Zertifizierungsstelle konfigurieren“Deploy PKCS#1 version 2.1 for a root CA (owned and issued certificates)
Before the Installation of a standalone root certification authority (Standalone Root CA) the question arises as to which cryptographic algorithms should be used.
Continue reading „PKCS#1 Version 2.1 für eine Stammzertifizierungsstelle (Root CA) einsetzen (eigenes und ausgestellte Zertifikate)“