[COMPASS-4853] Provide a disclaimer when users select SSL=None in "more options" for their connection Created: 26/May/21  Updated: 29/Oct/23  Resolved: 03/Mar/22

Status: Closed
Project: Compass
Component/s: Connectivity
Affects Version/s: None
Fix Version/s: 1.31.0

Type: Bug Priority: Minor - P4
Reporter: Ethan Steininger (Inactive) Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2021-05-26 at 9.31.10 AM.png    
Issue Links:
Depends
depends on COMPASS-5232 Add connection `TLS/SSL` tab form inputs Closed
Epic Link: COMPASS-4948
Story Points: 5
Documentation Changes: Not Needed

 Description   

Problem Description

When connecting to Atlas from Compass, I have the option of configuring the SSL requirements (so it seems) via the"more options" tab of compass (see screenshot). 

I interpret this SSL=None selection as us telling Compass not to use an SSL, but that's not the case from my understanding. In reality, it's telling Compass to not authenticate the validity of its' certificate with Atlas' (or whichever Mongo instance is used). 

Steps to Reproduce

Connect -> More Options -> SSL -> None

Expected Results

In addition to None (which should produce an error because Atlas' SRV records require SSL connections. Something like: "Don't authenticate Compass' SSL with the Server" would be more verbose and provide more clarity. 

Actual Results

SSL = None leads to confusion, because we're not actually removing SSL from the connection. 

Additional Notes



 Comments   
Comment by Maurizio Casimirri [ 03/Mar/22 ]

Fixed in 1.31 as we introduced a 3rd value that is for the default behavior and a warning to signal insecure connections

Generated at Wed Feb 07 22:37:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.