-
Type:
Bug
-
Status: Closed
-
Priority:
Minor - P4
-
Resolution: Fixed
-
Affects Version/s: 2.2.22
-
Fix Version/s: 2.2.23
-
Component/s: MongoDB 3.2
-
Labels:None
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';
|
|
|
// Use connect method to connect to the Server
|
MongoClient.connect(url, function(err, db) {
|
console.log("Connected correctly to server");
|
});
|
On the arbiter's logs, we see the following:
2017-02-09T21:02:12.750-0800 I NETWORK [initandlisten] connection accepted from IP:PORT #131448 (3 connections now open)
|
2017-02-09T21:02:12.753-0800 I ACCESS [conn131448] SCRAM-SHA-1 authentication failed for dbUser on dbName from client IP ; UserNotFound: Could not find user dbUser@dbName
|
Please let me know if you need anything else.