-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Security
-
None
-
Fully Compatible
-
ALL
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