MongoDB3 enterprise AuditLog

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.0.1, 3.1.0
    • Affects Version/s: 3.0.0
    • Component/s: Security
    • Fully Compatible
    • ALL
    • 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
    • Security 1 04/03/15
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Amalia Hawkins (Inactive)
            Reporter:
            Cory Morales
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: