server returned error on SASL authentication step: Authentication failed

Question

The following is my MongoDB connection dial from GoLang. But it's returning a panic "server returned error on SASL authentication step: Authentication failed.". My username, password, hostAddrs and dbName are correct. What am I missing here?

dbName: = os.Getenv("ENV_DBNAME")
userName: = os.Getenv("ENV_DBUSER")
password: = os.Getenv("ENV_DBPASS")
dbHost: = os.Getenv("ENV_DBHOST")
mongoDialInfo: = & mgo.DialInfo {
 Addrs: [] string {
  dbHost
 },
 Database: dbName,
 Username: userName,
 Password: password,
 Timeout: 60 * time.Second,
}
sess, err: = mgo.DialWithInfo(mongoDialInfo)
if (err != nil) {
 panic(err)

}

Solution 1

I faced similar error and added --authenticationDatabase parameter and it worked while we connecting to a remote MongoDB

Use the similar below format in your code :

$mongorestore --host databasehost:98761 --username restoreuser
--password restorepwd --authenticationDatabase admin --db targetdb ./path/to/dump/

Solution 2

Often we confused with parameter in the mongoexport command with "Log-In" user. The command expects "Database Username" not Log-in username. This is one possibility to input wrong user name. "Database Username" can be found in "Users" tab for a database

Solution 3

I got my answer from this link: https://newbiedba.wordpress.com/2016/11/21/mongodb-3-2-server-returned-error-on-sasl-authentication-step-authentication-failed/

Except for all answers above, the only unmentioned reason is that my password has a special character '$' in it. I think this is a very common practice to have special characters and this may trip many without this simple tip:

When using command line mongo/mongostat/etc.. Single quote your username or password that has special characters!

Solution 4

mgo returns this error if username, password or database are wrong. Check your credentials twice. There are no other situations when you can see Authentication failed error message.

Solution 5

The error you report seem the cause of the authentication fail is caused by a nil pointer, you should check the data before using them to create the connection

View more solutions

Comments

[Arjun Ajith]

server returned error on SASL authentication step: Authentication failed. panic: runtime error: invalid memory address or nil pointer dereference panic: runtime error: invalid memory address or nil pointer dereference

[CrazyCrow]

Yes this is correct way to implement connection. Here is working code gist.github.com/bearburger/718dec31746762684a7a512aed992a37 that connects demo DB.

[Rav]

Thanks, in my case that was exactly the solution.

[ahaurat]

In my case, I was using my mLab password instead of the db password. Silly mistake but this answer helped me figure it out!

[vabm]

I'm confused... what is the --authenticationDatabase parameter? the name of the database you want to access?

[alaster]

In my case I had access to only one db on server. So I needed to just add -d <dbname> option. No need of --authenticationDatabase for me

[rrw]

I dont know how the up-voter understood you, but I am sure I understood nothing from your answer. Mind elaborating more...?

[Bestbug]

Well after more than 1 year I don't know exactly what I was thinking. Probably my idea was the Golang application can't retreive one or more env_variable from the host.

[Zach B.]

Exactly my problem. Thank you.

[Pax Beach]

It is the right advice, but I had '%' sign in my password, and in the cmd.exe script the sign has disappeared. I had the same error =)

[Bruno Fernandes]

I had a ';' in my password!

[tyleax]

Thanks this was the solution after searching a while for what was wrong.

[Andrei Radulescu]

tl;dr "To solve the issue, simply single quote the password field." e.g. -p 'password'

[Jigar Prajapati]

changing few things and it's working thank you so much bhai

[Jack]

Thank you, I had a & which was causing the issue

[DummyBeginner]

My problem was using shorthands -u and -p even beside --authenticationDatabase in mongoimport. Replacing them with their long-form respectively ( --username and --password) along with the --authenticationDatabase solved the problem.

[Yonatan Naor]

You are my hero!