Error authentication failed mongodb

I create a user with the following set of commands. This should create user in both admin db as well as my target db (c2d):

# mongo 127.0.0.1:27017
MongoDB shell version: 3.2.6-29-g5c19788
connecting to: 127.0.0.1:27017/test
> use admin
switched to db admin
> show collections
system.users
system.version
> db.system.users.find()
> db.createUser({user:"cd2", pwd:"cd2", roles:[{role:"dbOwner", db: "c2d"}]})
Successfully added user: {
    "user" : "cd2",
    "roles" : [
        {
            "role" : "dbOwner",
            "db" : "c2d"
        }
    ]
}
> db.system.users.find()
{ "_id" : "admin.cd2", "user" : "cd2", "db" : "admin", "credentials" : { "SCRAM-SHA-1" : { "iterationCount" : 10000, "salt" : "4g6t9kC+godz7k6QQOfD+A==", "storedKey" : "m3tDZBQDU2Tlb1lIjLGyTHmr2QQ=", "serverKey" : "GSA4OXSod1s8mBuZBtfmXq2tlTo=" } }, "roles" : [ { "role" : "dbOwner", "db" : "c2d" } ] }
> use c2d
switched to db c2d
> db.createUser({user:"cd2", pwd:"cd2", roles:[{role:"dbOwner", db: "c2d"}]})
Successfully added user: {
    "user" : "cd2",
    "roles" : [
        {
            "role" : "dbOwner",
            "db" : "c2d"
        }
    ]
}
> use admin
switched to db admin
> db.system.users.find()
{ "_id" : "admin.cd2", "user" : "cd2", "db" : "admin", "credentials" : { "SCRAM-SHA-1" : { "iterationCount" : 10000, "salt" : "4g6t9kC+godz7k6QQOfD+A==", "storedKey" : "m3tDZBQDU2Tlb1lIjLGyTHmr2QQ=", "serverKey" : "GSA4OXSod1s8mBuZBtfmXq2tlTo=" } }, "roles" : [ { "role" : "dbOwner", "db" : "c2d" } ] }
{ "_id" : "c2d.cd2", "user" : "cd2", "db" : "c2d", "credentials" : { "SCRAM-SHA-1" : { "iterationCount" : 10000, "salt" : "vnMjnjfykVQS8ujQXeWaYw==", "storedKey" : "OYXivkmIwuTavlwTGfjrspT6j2E=", "serverKey" : "lw8xqzAaW8V4IQ9wOmQrG2VSp88=" } }, "roles" : [ { "role" : "dbOwner", "db" : "c2d" } ] }

If I try to login, I’m welcomed with an error message:

# mongo 127.0.0.1:27017/c2d -u c2d -p c2d
MongoDB shell version: 3.2.6-29-g5c19788
connecting to: 127.0.0.1:27017/c2d
2016-05-22T10:35:41.862+0100 E QUERY    [thread1] Error: Authentication failed. :
DB.prototype._authOrThrow@src/mongo/shell/db.js:1441:20
@(auth):6:1
@(auth):1:2

exception: login failed

Then I enable security features in the conf file and restart the server:

security:
  authorization: enabled

Error is still the same:

# mongo 127.0.0.1:27017/c2d -u c2d -p c2d
MongoDB shell version: 3.2.6-29-g5c19788
connecting to: 127.0.0.1:27017/c2d
2016-05-22T10:37:43.713+0100 E QUERY    [thread1] Error: Authentication failed. :
DB.prototype._authOrThrow@src/mongo/shell/db.js:1441:20
@(auth):6:1
@(auth):1:2

exception: login failed

Securing data is always a primary concern in database management.

Usually, MongoDB error auth failed, occurs when using an improper authentication method.

To restrict MongoDB we need to add an admin user and then enable access control.

At Bobcares, we often get requests to fix MongoDB errors, as a part of our Server Management Services.

Today, let’s discuss how our Support Engineers enable access control in MongoDB.

Auth failed error in MongoDB

Authentication is important for preventing unauthorized access. By enabling auth, MongoDB verifies the users to determine their access.

Users will have well-defined roles and it’s important to verify it before using the database. This is to ensure security over the data stored.

Usually, MongoDB shows auth failed errors when it uses an improper auth method.

When a user tries to access the database using the auth user, it shows up the error as,

Here, MongoDB could not identify the user. This indicates that the auth method was not proper. As a result, the login attempt ends up in a failed status.

Method to enable Authentication in MongoDB

Authentication adds security over any system. But, enabling access control in MongoDB databases often shows errors.

Usually, this is because of improper auth methods. Our Dedicated Engineers with expertise over a decade enables auth in databases. Now, let’s discuss how we authenticate a user in the MongoDB server.

Step 1: Create an admin user

Initially, to enable access control our Support Engineers create an admin user. In the mongod shell, we add a user with admin privilege in the admin database.

use admin
db.createUser(
{
user: "myUserAdmin",
pwd: passwordPrompt(),
roles: [ { role: "userAdminAnyDatabase", db: "admin" }, "readWriteAnyDatabase" ]
}
)

Further, we restart the mongod shell as an admin user. Firstly, we shut down the currently using shell. And, to start again we use the command,

mongod --auth --port 27017 --dbpath <dbpath>

Usually, there are two ways to enable access control. That is, either during connection or after connecting.

a. Authenticate during connection

To authenticate a user during connecting we use the command,

mongo --port 27017 --authenticationDatabase "admin" -u "myUserAdmin" -p

Now, we enter the password when prompted. This successfully enables access control to the admin user.

Hence, the admin user can now add as many users as needed.

b. Authenticate after connecting

On the other hand, we can authenticate the user after connecting. To connect to mongo shell, we use the command,

mongo --port 27017

Now we have entered the shell. Next, we switch to admin using the command,

use admin
db.auth("myUserAdmin", passwordPrompt())

Here, we enter the password. Hence, now the admin user has permission to create a new user.

Step 2: Creating users and authenticating

So far, we have created an admin user. This admin user can now create new users. Afterward, the admin user can authenticate new users.

Firstly, our Support Engineers create a new user as we created the admin user.

We give access control to the user as required. Now, we have a newly created auth user. In addition, to ensure the auth we enter the mongo shell using the created user.

Finally, our MongoDB Experts check the config file to see the security authorization parameter. The mongod.conf appear as

Application-specific auth

By default, MongoDB users are scoped to particular databases. Therefore, even if the users have cross-DB privileges, authentication may not work. That is if the user isn’t defined on DB auth will simply fail.

That’s why, in applications like Mongoose, we enable auth using the format:

mongoose.connect('mongodb://user:password@host/yourDB?authSource=yourDB&w=1')

[Still having difficulty in fixing MongoDB errors? – We’ll fix it.]

Conclusion

In short, MongoDB error Auth failed occurs due to improper enabling of access control. Today, we saw how our Support Engineers enable authentication for MongoDB users.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

I have made connection to cloud.mongodb.com with node.js but I don’t understand why and how I made 2 successful connections but other times connections were unsuccessfull .

In Console I see

the server/replset/mongos options are deprecated, all their options are supported at the top level of the options object [poolSize,ssl,sslValidate,sslCA,sslCert,sslKey,sslPass,sslCRL,autoReconnect,noDelay,keepAlive,connectTimeoutMS,fa
mily,socketTimeoutMS,reconnectTries,reconnectInterval,ha,haInterval,replicaSet,secondaryAcceptableLatencyMS,acceptableLatencyMS,connectWithNoPrimary,authSource,w,wtimeout,j,forceServerObjectId,serializeFunctions,ignoreUndefined,raw,bu
fferMaxEntries,readPreference,pkFactory,promiseLibrary,readConcern,maxStalenessSeconds,loggerLevel,logger,promoteValues,promoteBuffers,promoteLongs,domainsEnabled,keepAliveInitialDelay,checkServerIdentity,validateOptions,appname,auth]

(node:3268) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): MongoError: authentication fail
(node:3268) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Hey 😍

Want to help the DEV Community feel more like a community?

Head over to the Welcome Thread and greet some new community members!

It only takes a minute of your time, and goes a long way!

Getting data is for the most part a central fear in the informational index parties. MongoDB screw-up auth failed, happens while using an improper confirmation procedure. To bind MongoDB, we need to add a manager customer and thereafter enable access control.

Around here at ARZHOST, we routinely get requests to fix MongoDB errors, as a piece of our Server Management Services.

Today at arzhost.com, “Uncaught Mongo DB Error – Authentication Failed” could we analyze how our Hosting Expert Planners engage access control in MongoDB.

Auth attacked error in MongoDB

Confirmation is huge for hindering unapproved access. By enabling auth, MongoDB looks at the customers to choose their entry. Customers will play obvious parts and it’s essential to look at it before using the informational collection. This is to ensure security over the data set aside.

Generally, MongoDB shows auth attacked errors when it uses an improper auth method. Exactly when a customer actions to get to the database using the auth customer, it seems the slip-up as,

Here at arzhost.com, MongoDB couldn’t perceive the customer. This shows that the auth strategy was not proper. Consequently, “Uncaught Mongo DB Error – Authentication Failed” the login attempt ends up in an attacked status.

Procedure to engage Authentication in MongoDB

The statement adds security over any structure. In any case, enabling access control in MongoDB informational collections routinely shows errors.

Ordinarily, this is a consequence of unseemly auth methods. Our Hosting Expert Planners with governance over 10 years enable auth in informational indexes. “Uncaught Mongo DB Error – Authentication Failed” By and by, could we inspect how we approve a customer in the MongoDB server.

Stage 1: Create a director customer

From the beginning, to engage access control our Hosting Expert Planners make a management customer. In the MongoDB shell, we add a customer with overseer honor in the head database.

• use chairman
• create User (
• {
• customer: "myUserAdmin",
• pwd: password Prompt (),
• occupations: [ {work: "userAdminAnyDatabase", db: "chairman”}, "readWriteAnyDatabase”]
• }
• )

Extra, we restart the MongoDB shell as an executive customer. First thing, we shut down the by and by using the shell. Additionally, to start again we use the request:

• MongoDB - - auth-port 27017 - - dB path <dB path>

For the most part, there are two techniques for enabling access control. “Uncaught Mongo DB Error – Authentication Failed” That is, either during affiliation or following interacting.

A: Confirm during affiliation

To confirm a customer during shared we use the request,

• mongo - - port 27017 - - authentication Database "director" - u "my user admin" - p

By and by, we enter the mystery key when prompted. This viably enables access control to the head customer.

Consequently, the manager customer can now add anyway numerous customers relying upon the circumstance.

B: Confirm right after interacting

On the other hand, we can check the customer following interaction. To communicate with mongo shell, we use the request:

• mongo - - port 27017

By and by we have entered the shell. Then, at that point, we change to the manager using the request:

• use chairman
• Auth (“my user admin”, password Prompt ())

Here at arzhost.com, “Uncaught Mongo DB Error – Authentication Failed” we enter the mystery word. Later, by and by the chairman customer has the approval to make another customer.

Stage 2: Creating customers and confirming

Up until this point, we have made an overseer customer. This director customer can now make new customers. A brief time frame later, the head customer can confirm new customers.

First thing, our Hosting Expert Planners make one more customer as we made the manager customer.

We give access control to the customer as required. By and by, we have an as of late made auth customer. “Uncaught Mongo DB Error – Authentication Failed” Besides, to ensure the auth we enter the mongo shell using the made customer.

Finally, our MongoDB Experts check the config report to see the security confirmation limit. The MongoDB. conf appears as.

Application-express auth

Normally, MongoDB customers are checked to explicit informational indexes. As such, whether or not the customers have cross-DB approvals. “Uncaught Mongo DB Error – Authentication Failed” confirmation may not work. That is in case the customer isn’t described on DB auth will miss the mark.

That is the explanation, in applications like Mongoose, we engage auth using the arrangement:

• connect('mongodb://user:password@host/yourDB?authSource=yourDB&w=1')

Mongo Error: Authentication failed

It might be disappointing to begin a dissecting action, and get a message like Mongo Error: Authentication failed. Particularly, if you hate MongoDB Compass.

A couple of ordinary issues might be with entries on the Auth tab: are the username and mystery word spelled precisely, with the legitimate upper and lower cases, and is the Auth source right (a significant part of the time it should be left unfilled or use the default “manager”.)

However, there could be various hints. “Uncaught Mongo DB Error – Authentication Failed” Compass and ARZHOST use comparable programming libraries to connect with MongoDB events, whether or not on-premises or Atlas.

Just to guarantee that the connection string is vague from what you have in Compass, is to copy/stick from Compass into ARZHOST. Here are the means:

• Open Compass, select the affiliation, and snap on the Edit button:
• Click Confirm
• in the change window, press ctrl+A to pick the entire string, then, ctrl+C to copy the string to the clipboard:
• In ARZHOST MongoDB model affiliations settings, add another, and press the button “From SRV or URI”:
• then, press ctrl+V or right-snap and pick stick:

Right when you save, this should parse the string and fill in all of the entries thus. Then, effort again to connect with the database. “Uncaught Mongo DB Error – Authentication Failed” using the as of late made connection settings.

Termination

Thus, MongoDB error Auth failed occurs due to improper enabling of access control. Today at arzhost.com, “Uncaught Mongo DB Error – Authentication Failed” we saw how our Hosting Expert Planners enable approval for MongoDB customers.

Read More

MongoDb Shutting Down with Code 100

As per your log statement it seems like that you are committing mistake in your authentication statement such as in your statement

mongo 127.0.0.1:27017 --authenticationDatabase admin -u admin -p

As per MongoDB BOL documentation here With access control enabled, ensure you have a user with userAdmin or userAdminAnyDatabase role in the admin database. This user can administrate user and roles such as: create users, grant or revoke roles from users, and create or modify customs roles.

Connect and authenticate as the user administrator

Using the mongo shell, you can:

• Connect with authentication by passing in user credentials, or

• Connect first withouth authentication, and then issue the db.auth()
  method to authenticate.

For example, the following creates the user myUserAdmin in the admin database:

use admin
db.createUser(
  {
    user: "myUserAdmin",
    pwd: "abc123",
    roles: [ { role: "userAdminAnyDatabase", db: "admin" } ]
  }
)

To authenticate during connection

Start a mongo shell with the -u , -p , and the —authenticationDatabase command line options:

mongo --port 27017 -u "myUserAdmin" -p "abc123" --authenticationDatabase "admin"

To authenticate after connecting

Connect the mongo shell to the mongod:

mongo --port 27017

Switch to the authentication database (in this case, admin), and use db.auth(<username>, <pwd>) method to authenticate:

use admin
db.auth("myUserAdmin", "abc123" )

As I am able to see that in your below mention mongod.conf file the authorization : enable . It’s means your authentication is enable. So, there is no issue in your mongod.conf file.

systemLog:
  destination: file
  path: /Users/me/Web/blog/setup/logs/mongodb/mongo.log
  logAppend: true
storage:
  dbPath: /usr/local/var/mongodb
net:
  port: 27017
  bindIp: 127.0.0.1
security:
  authorization: enabled

For your further ref here and here