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

Access Control not logging successful logins on MongoDB 3.4 Community

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Admin, Security
    • None
    • ALL

      After adjust the verbosity of the parameter "accessControl" with the command:
      'db.setLogLevel(5,"accessControl")'

      The log file still not login successful login.

      On mongo 3.2:
      2017-04-20T15:56:06.661+0200 I ACCESS [conn16895093] Successfully authenticated as principal username on admin

      On mongo 3.4:
      Only unsuccessful auth like:
      2017-04-25T15:07:04.478+0200 I ACCESS [conn291586] SCRAM-SHA-1 authentication failed for username on admin from client 127.0.0.1:37171 ; AuthenticationFailed: SCRAM-SHA-1 authentication failed, storedKey mismatch

      So I can NOT upgrade my environment from 3.2 to 3.4 safely.

      Best Regards

        1. auth_command_get_get_users_2.log
          0.6 kB
        2. auth_command_get_get_users.log
          0.5 kB
        3. mongod_log_wrong_auth.log
          8 kB
        4. mongod.conf
          0.7 kB

            Assignee:
            mark.agarunov Mark Agarunov
            Reporter:
            jefersonlucascs Jeferson Lucas da Costa Santana
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: