[COMPASS-2846] Validate TLS 1.2 Support with MongoDB 4.0 Created: 14/May/18 Updated: 12/Jun/18 Due: 26/Jun/20 Resolved: 10/Jun/18 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Compass |
| Affects Version/s: | None |
| Fix Version/s: | 1.14.0, 1.15.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matt Lord (Inactive) | Assignee: | Durran Jordan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Epic Link: | PRODUCT-774 |
| Story Points: | 2 |
| Sprint: | Sprint Xzibit |
| Description |
|
We need to verify that the latest version of Compass can connect to a MongoDB 3.7.9/4.0.0 instance with --requireSSL enabled [--sslDisabledProtocols=TLS1_0] (1.0 is disabled by default). This is enough to mark Compass as done with regards to the company/product wide Safe TLS initiative driven by the PCI-DSS deadline of June 30, 2018 where TLS 1.0 must be disabled by default everywhere. |