Cannot connect with authMechanism Legacy SCRAM SHA-1

I exported a connection URI from Studio 3T, and used the From URI feature in NoSQLBooster. Here's the URI (with modified user/password):

mongodb://username:password@ARDUVGOIISW03:27017/admin?readPreference=primary

If I create the connection in JSON like you posted above, I have questions:

1) Where should I paste that JSON (or save as a file), and how do I import/create a new connection from that?

2) How can I specify my password in plain text? That's how I enter the password in S3T, and then S3T encrypts it for local storage. So I need to be able to specify it as plain text OR can you tell me how to encrypt it like you have in the JSON you posted?

Below is a screenshot of the connection test I did from NSB, and also a screenshot of testing the same connection from S3T.

Thanks!

Ken

1) First, check to see if the firewall has blocked the connection, If you have an anti-virus, you can also try to disable it. Some could also block the connection. The error getaddrinfo ENOTFOUND ARDUVGOIISW03 is caused by MongoDB NodeJS driver cannot found ARDUVGOIISW03 address.

2) Please try the following URI (delete ?readPreference=primary)

mongodb://username:password@ARDUVGOIISW03:27017/admin

NoSQLBooster's Basic(Username/Password) auth mode supports both SCRAM-SHA-256, SCRAM-SHA-1 and MONGODB-CR.

qinghai, thank you! I used IP address instead of hostname and the connection worked! Next I used fully-qualified name (ARDUVGOIISW03.universalweather.rdn) and that worked!

Apparently the other tools I had been trying were okay with just the hostname but NSB is not?

Anyway, problem solved. Thank you for your help!

Ken

If you have a nodejs runtime environment, can you do a simple test for me, I want to confirm if the problem is caused by the nodejs mongodb driver.

1) Create a test project directory, and CD to this directory

2) Save the following script as index.js

const MongoClient = require('mongodb').MongoClient;
const assert = require('assert');

// Connection URL
const url = 'mongodb://username:password@ARDUVGOIISW03:27017/admin';

// Database Name
// Use connect method to connect to the server

MongoClient.connect(url, function(err, client) {
  assert.equal(null, err);
  console.log("Connected successfully to server");

  client.close();
});

4) cmd > node index.js

If mongodb@3.1.7 does not work, please unisntall mongodb@3.1.7 and install the mongodb@latest and try it again.

Hello qinghai,

I finally tried your test. Here is what I got:

C:\Users\kdellinger\src\mdb\test>npm i mongodb@3.1.7 
npm notice created a lockfile as package-lock.json. You should commit this file. 
npm WARN test@1.0.0 No repository field. 

+ mongodb@3.1.7 
added 10 packages from 7 contributors and audited 11 packages in 1.758s 
found 0 vulnerabilities 

C:\Users\kdellinger\src\mdb\test>node index.js 
(node:237012) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect. 
C:\Users\kdellinger\src\mdb\test\node_modules\mongodb\lib\operations\mongo_client_ops.js:466 
      throw err; 
      ^ 

AssertionError [ERR_ASSERTION]: null == 
                

Thank you for your feedback.

From the results of your feedback, this issue is indeed at the driver level of mongodb nodejs. Because I can't reproduce it locally, it's hard to locate, and it seems to be difficult to solve for the time being.

Thanks for trying. :)

Using the fully-qualified hostname works fine, so maybe if the hostname field for the connection had a hint about that so any new users would not have difficulty . . . just a suggestion.

Ken