Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-12693

Inserting an invalid doc into new_users and setting authSchemaVersion to 2 makes auth fail after authSchemaUpgrade

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Security
    • Labels:
      None

      See https://github.com/10gen/QA/blob/master/QA-424/sharded_upgrade_invalid_new_users.js

      Essentially what this test does is:

      1) Set up a 2.4 sharded cluster with 2 users
      2) Manually insert a bad document into admin.system.new_users
      3) Upgrade to 2.5.x
      4) Set authSchema currentVersion to 2
      5) Run authSchemaUpgrade

      What ends up happening is that the auth schema version is 3, but I'm unable to log in after the upgrade. Any ideas what's going on here?

            Assignee:
            schwerin@mongodb.com Andy Schwerin
            Reporter:
            valeri.karpov@mongodb.com Valeri Karpov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: