[SERVER-18103] Cannot copydb from a replica set without auth to a sharded cluster with auth Created: 17/Apr/15  Updated: 14/Jul/17  Resolved: 14/Jul/17

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

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Looks like if you try to run copydb on a sharded cluster with auth on and point it to an unsecured replica set, it tries to authenticate to the replica set as the internal user, which fails, and causes the copydb command to fail saying it cannot connect to the source replica set



 Comments   
Comment by Mira Carey [ 14/Jul/17 ]

Product has told me that mongo mirror does this

Comment by Githook User [ 17/Apr/15 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-18103 Fix copyauth.js to run all permutations except skip one that is currently broken
Branch: master
https://github.com/mongodb/mongo/commit/32be1f06790c71cdb99f61d40dbe02f7245195bc

Generated at Thu Feb 08 03:46:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.