-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Environment:OS:
node.js / npm versions:
Additional info:
-
Not Needed
-
Developer Tools
Problem Statement/Rationale
The MongoDB clusters are configured with "requiredTLS". There are no issues really with TLS.
The client has issues with Compass because their Certificate Store in Windows may contain valid and expired certificates. "mongosh" consistenly chooses the valid certificates to connect. However, Compass selects expired certificates not always but most of the time. With the latest release of Compass, things have gotten worse for this client.
Please be sure to attach relevant logs with any sensitive data redacted.
How to retrieve logs for: Compass; Shell
Steps to Reproduce
How could an engineer replicate the issue you’re reporting?
Expected Results
Do not use expired certificates if there is another certificate that would match and is not expired.
Actual Results
What do you observe is happening?
Additional Notes
Customer's help case: https://hub.corp.mongodb.com/case/01359379
- related to
-
COMPASS-8322 Expired certificates in the CA list cause connections to fail
- Closed
-
COMPASS-8253 Set X509_V_FLAG_PARTIAL_CHAIN when connecting
- Closed