Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-1318

Authentication attempts against arbiter node

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor - P4
    • Resolution: Fixed
    • 3.0.0, 3.0.1, 3.0.2
    • 3.2.2
    • Core, MongoDB 3.4

    Description

      Since 3.0, the driver is attempting to authenticate against the arbiter node. This script reproduces the issue:

      ```

      var MongoClient = require('mongodb').MongoClient;
      		 
       
      var url = 'mongodb://dbUser:dbPass@primary,secondary/dbName?replicaSet=rsname';
      		 
       
      MongoClient.connect(url, (err, client) => {
      		 
        console.log("Connected correctly to server");
      		 
      });

      On the arbiter's logs:

      2018-02-07T10:43:36.930-0800 I NETWORK  [thread1] connection accepted from <ip>:<port> #11241 (3 connections now open)
      		 
      2018-02-07T10:43:36.931-0800 I ACCESS   [conn11241] SCRAM-SHA-1 authentication failed for <dbuser> on <dbname> from client <ip>:<port> ; UserNotFound: Could not find user <dbuser>@<dbname>
      		 
      2018-02-07T10:43:37.045-0800 I -        [conn11241] end connection <ip>:<port> (3 connections now open)

      Related issues from previous versions: NODE-927, NODE-981

      Please let me know if you need anything else.

      Attachments

        Issue Links

          depends on

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. NODE-1290 SDAM Refactor

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

          Activity

            People

              daniel.aprahamian@mongodb.com Daniel Aprahamian (Inactive)
              tfogo Tim Fogarty
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: