copyDatabase fails authentication when source db has legacy system.users collection

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Incomplete
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.6.4
    • Component/s: Security
    • None
    • ALL
    • Hide

      1. Upgrade database with legacy authentication (i.e. system.users collection in the non-admin db)
      2. In a second server try to run the db.copyDatabase command with correct authentication/authorization.

      Show
      1. Upgrade database with legacy authentication (i.e. system.users collection in the non-admin db) 2. In a second server try to run the db.copyDatabase command with correct authentication/authorization.
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      All databases running latest MongoDB 2.6.4 on Ubuntu.

      After upgrading from 2.4 -> 2.6 I tried to use the db.copyDatabase() command to copy a remote database from a production server to a test server, but always get an error that I don't have permission on the "system.users" collection. I am not able to drop this legacy collection, even when user has role 'root'.

      If I create a brand new database on the remote machine with the same user authorization, I can copy this successfully. I have also tried every permutation of db.copyDatabase and the copyDB command and granted both remote and local users every possible role including root.

            Assignee:
            Spencer Brody (Inactive)
            Reporter:
            Ben Trombley
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: