[SERVER-2931] cloneCollection & authentication Created: 11/Apr/11 Updated: 06/Dec/22 Resolved: 02/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | 1.8.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Gaetan Voyer-Perrault | Assignee: | Backlog - Security Team |
| Resolution: | Won't Fix | Votes: | 22 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Security
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Clone collection does not allow for cloning of data requiring authentication. Should probably be something like the following: |
| Comments |
| Comment by Spencer Jackson [ 02/Jan/20 ] |
|
I am closing this issue as the cloneCollection command has been deprecated. |
| Comment by Ranjith Ramachandra [ 06/May/14 ] |
|
Mongo developers, Why isn't this feature important? We have a lot of use for this cloneCollection method. only way is to do this in the application layer... |
| Comment by Sean Macdonald [ 04/Apr/12 ] |
|
or perhaps: { "cloneCollection":"blank.test", "from":"mongodb://myusername:mypassword@127.0.0.1:27017", "copyIndexes":true } |