[COMPASS-5058] Combine Client Certificate and Client Key file into a single input to match tlsCertificateKeyFile and VSCode Created: 02/Sep/21 Updated: 11/Nov/21 Resolved: 11/Nov/21 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Michael Rose (Inactive) | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Epic Link: | COMPASS-4948 | ||||||||||||||||||||
| Documentation Changes: | Not Needed | ||||||||||||||||||||
| Description |
|
Right now the user has to select both a "Client Certificate" and a "Client Private Key" file in Compass when using "Server and Client Validation". These two options cannot be converted into a plain connection string, as the connection string URI options spec (https://github.com/mongodb/specifications/blob/master/source/uri-options/uri-options.rst) only has the tlsCertificateKeyFile parameter which requires certificate and key to be combined into a single file. VSCode already only provides a single field "Client Certificate and Key" and Compass should do the same. |
| Comments |
| Comment by Maurizio Casimirri [ 11/Nov/21 ] |
|
This will be implicitly implemented with the new design |