-
Type: Bug
-
Resolution: Fixed
-
Priority: Minor - P4
-
Affects Version/s: None
-
Component/s: Connectivity
-
None
-
5
-
Not Needed
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
- depends on
-
COMPASS-5232 Add connection `TLS/SSL` tab form inputs
- Closed