Localhost exception not working on Windows with LDAP authorization

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.4.0-rc1
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Hide

      Configure a Windows Server 2012 box as a domain controller. Call the computer WINTEST and the domain MONGODB.LOCAL. Set the password for the Administrator account to "Test123!" Extract the attached zip file with MongoDB configuration files to C:\MMSAutomation. Start a mongod with each configuration file under data and a mongos with the configuration file under versions\workspace. Initiate two replica sets, one on ports 27000, 27001, and 27002, and the other on ports 27003, 27004, and 27005. Initiate the config server replica set, containing just one node, on port 27019. Connect to the mongos by running the Mongo shell with no parameters. Then, run the following:

      use admin
db.system.roles.findOne()

      There will be an authorization error, although access should be allowed under the localhost exception.

      Show
      Configure a Windows Server 2012 box as a domain controller. Call the computer WINTEST and the domain MONGODB.LOCAL. Set the password for the Administrator account to "Test123!" Extract the attached zip file with MongoDB configuration files to C:\MMSAutomation. Start a mongod with each configuration file under data and a mongos with the configuration file under versions\workspace. Initiate two replica sets, one on ports 27000, 27001, and 27002, and the other on ports 27003, 27004, and 27005. Initiate the config server replica set, containing just one node, on port 27019. Connect to the mongos by running the Mongo shell with no parameters. Then, run the following: use admin db.system.roles.findOne() There will be an authorization error, although access should be allowed under the localhost exception.
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When attempting to use LDAP authorization on Windows with a sharded cluster, the localhost exception doesn't work, making it impossible to add the role for the Automation Agent.

      CC tim.olsen dennis.kuczynski

        1. db.zip
          8 kB

            Assignee:
            Andreas Nilsson (Inactive)
            Reporter:
            David Golub (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: