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

MongoDB3 enterprise AuditLog

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.0.0
    • Fix Version/s: 3.0.1, 3.1.0
    • Component/s: Security
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Steps To Reproduce:
      Hide

      1. In your mongoDB config yaml set up audit logging like so
      security:
      authorization: enabled
      auditLog:
      destination: file
      format: JSON
      path: "C:/data/db/auditLog.json"
      filter: '

      { atype: "authenticate"}

      '

      2.) db.auth('','') with incorrect credentials and see that the failure is not logged in the AuditLog like it was before

      Show
      1. In your mongoDB config yaml set up audit logging like so security: authorization: enabled auditLog: destination: file format: JSON path: "C:/data/db/auditLog.json" filter: ' { atype: "authenticate"} ' 2.) db.auth('','') with incorrect credentials and see that the failure is not logged in the AuditLog like it was before
    • Sprint:
      Security 1 04/03/15

      Description

      The AuditLog is not logging authentication failures in 3.0 enterprise and only logging the successes. This was working fine in version 2.6 enterprise.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: