[SERVER-13118] Make copydb capable of using all authentication mechanisms Created: 10/Mar/14 Updated: 14/Jul/17 Resolved: 14/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | 2.4.9, 2.6.0-rc1 |
| 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: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Copydb can copy a database from a remote mongodb cluster. If auth is enabled on the remote cluster, you can provide a username and password to copydb, and copydb will attempt to authenticate to the remote cluster using the username and password provided, using the MONGODB-CR authentication mechanism. If the remote server has MONGODB-CR disabled, however, in favor of Kerberos, LDAP, or X509 authentication, copydb cannot authenticate to it. |
| Comments |
| Comment by Mira Carey [ 14/Jul/17 ] |
|
the server currently supports sasl with copydb. The others should just work, excepting x509, which we don't believe has a sane implementation |
| Comment by Spencer Brody (Inactive) [ 10/Mar/14 ] |
|
Make sure to undo the changes made to test files as part of |