[SERVER-32713] Support different authentication databases when using db.copyDatabase() Created: 16/Jan/18 Updated: 06/Apr/23 Resolved: 17/Jan/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.6.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Lowe | Assignee: | Mark Agarunov |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently db.copyDatabase will try to authenticate the user credentials in the specified source database, and it's not possible to authenticate with users from another database (e.g. admin). This makes copyDatabase unusable for setups where users are stored in admin database. Ideally copyDatabase should accept an extra parameter, allowing authentication database to be specified. |
| Comments |
| Comment by Mark Agarunov [ 17/Jan/18 ] |
|
Hello sosh, After looking into this some more, it appears that it is a request for the same behavior as detailed in Thanks, |
| Comment by Mark Agarunov [ 16/Jan/18 ] |
|
Hello sosh, Thank you for the example. I've set the fixVersion to "Needs Triage" for this new feature to be scheduled against our currently planned work. Updates will be posted on this ticket as they happen. Thanks, |