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

MongoDB3 enterprise AuditLog

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.0.0
    • 3.0.1, 3.1.0
    • 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

    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

          related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-17516 Add audit log messages for using incorrect auth mechanisms.

          • Major - P3 - Major loss of function.
          • Open

          Activity

            People

              amalia.hawkins@10gen.com Amalia Hawkins
              coryales1@gmail.com Cory Morales
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: