[SERVER-25162] Make SSL connection for copyDatabase() to be optional Created: 20/Jul/16  Updated: 15/Sep/16  Resolved: 20/Jul/16

Status: Closed
Project: Core Server
Component/s: Networking, Security
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Dmitry Ryabtsev Assignee: Ramon Fernandez Marina
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-11528 Add option to copyDB and clone comman... Closed
Related
Participants:

 Description   

If instance is started with SSL enabled (e.g. Atlas) and if db.copyDatabase() is executed - the mongod will attempt to establish outbound connection with SSL. Effectively that makes it impossible for users to use copyDatabase() for data migration into an Atlas cluster as the target mongod, if started without SSL, will process SSL handshake and if it uses SSL, the certificate validation is likely to fail.

Perhaps we could make SSL use for the outbound connection to be optional? (for copyDatabase() only)


Generated at Thu Feb 08 04:08:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.