[COMPASS-4317] Use a single CertKey file picker on the connect form Created: 03/Jun/20  Updated: 10/Jan/24  Resolved: 24/Feb/22

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

Type: Task Priority: Major - P3
Reporter: Alena Khineika Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: COMPASS-4948
Documentation Changes: Not Needed

 Description   

To have a matching behavior for both VSCode and Compass apps use a single CertKey file picker on the connect form instead of having two separate fields for certificate and key. The `sslCert` and `sslKey` node driver options accept the same file type and `sslCert` can be used to accept a single file that contains both certificate and key.

https://mongodb.github.io/node-mongodb-native/3.6/api/MongoClient.html#.connect

The old documentation always sets both the cert and key, but they do the same thing. 
It is all linked to cert and key here https://nodejs.org/api/tls.html#tls_tls_connect_options_callback which supports "certificate chaining".
 
Note SSL options are deprecated but still supported. If specified both TLS and SSL options the TLS will override the SSL options because they are just aliases.



 Comments   
Comment by Rhys Howell [ 24/Feb/22 ]

This is done in the new connect form 🎆

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