Skip to content

Commit 6ca5bdd

Browse files
authored
docs: add troubleshooting section for certificates with identical subjects (#22238)
Document that the integration identifies certificates by subject, not serial number. When multiple certificates share the same subject, only one may be detected. Solution is to delete expired certificates from the Windows Certificate Store. Fix typo: Begnning → Beginning
1 parent 6eda036 commit 6ca5bdd

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

windows_certificate/README.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ instances:
5555
enable_crl_monitoring: true
5656
```
5757

58-
Begnning with Agent v7.70, the integration can validate certificates and their certificate chains. To enable the certificate chain validation, set the following in the integration:
58+
Beginning with Agent v7.70, the integration can validate certificates and their certificate chains. To enable the certificate chain validation, set the following in the integration:
5959
```yaml
6060
instances:
6161
- certificate_store: CA
@@ -92,6 +92,12 @@ See [service_checks.json][8] for a list of service checks provided by this integ
9292

9393
## Troubleshooting
9494

95+
### Certificates with identical subjects
96+
97+
The integration identifies certificates primarily by their subject, not by serial number. When multiple certificates share the same subject but have different serial numbers (for example, an expired certificate and its renewed replacement), the integration may only detect one of them, often the expired certificate.
98+
99+
**Solution**: Delete the expired certificate from the Windows Certificate Store so only the valid, renewed certificate is monitored. While `certificate_serial_number` is available as a tag on metrics and service checks, it cannot be used for filtering in the configuration. The integration only supports filtering by `certificate_subjects`.
100+
95101
Need help? Contact [Datadog support][9].
96102

97103

0 commit comments

Comments
 (0)