MongoDB replica set with simple password authentication

Question

I have a MongoDB replica set of 3 servers (1 primary, 1 secondary, 1 arbiter; this is the default replica set created by Google Cloud 1-click install). The 2 config files (mongod.conf) of primary server and secondary server have been changed with security.authorization: enabled added.

Root user is added with the following MongoDB shell command:

use admin db.createUser({user:"root",pwd:"root",roles:["root"]})

After restarting MongoDB services on the primary and secondary servers with "sudo service mongod restart", connection to the replica set turns unstable.

rs.status() sometimes give the result as

1 primary, 1 unreachable, 1 arbiter
1 secondary, 1 secondary, 1 arbiter
1 secondary, 1 unreachable, 1 arbiter

How to setup basic password authentication (not using keyfile) for MongoDB replica set the correct way?

Please provide the full output of rs.status() which you are observing. — helmy
– helmy, Commented Jul 22, 2016 at 13:27
Also, can you be more specific about what you mean by "unstable"? Is the rs.status() observed constantly like this? Only for a sure period? Intermittent? — helmy
– helmy, Commented Jul 22, 2016 at 13:29
hey man actually i am facing an error Error: couldn't add user: not authorized on admin to execute command. You can also find my question here stackoverflow.com/questions/41783700/… . It would be a lot much easier if you could tell me from which url(source) you have done this whole password authentication thing, please help me i have searched everywhere but didn't find anything ?? — Sudhanshu Gaur
– Sudhanshu Gaur, Commented Jan 21, 2017 at 22:02
use admin first to authenticate, then db.auth('username','password') — Marvin Lacuna
– Marvin Lacuna, Commented Apr 19, 2017 at 6:55

Dan D · Accepted Answer · 2019-07-31 09:59:05Z

33

I finally found the answer. MongoDB replica set needs both user account and keyfile. Keyfile seems for authentication between servers in the replica set, not for logging in.

Create mongodb key file on linux, copy to all db servers with mode 600 intact:

cd openssl rand -base64 741 > mongodb.key chmod 600 mongodb.key

mongod.conf file:

replication: replSetName: rs0 security: authorization: enabled keyFile: /home/USERNAME/mongodb.key

Admin user:

(just like in question content)

edited Jul 31, 2019 at 9:59

answered Jul 25, 2016 at 4:48

Dan D

8,7697 gold badges48 silver badges80 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

Gurkha Over a year ago

I have the same issue right now, I generated the key and provided it into individual .conf files, 4 in my case. now when i start the mongod without authentication it cant do rs.initiate() or create users. Do you know why?

Dan D Over a year ago

create user before creating replicaset, rs.initiate on first server only. "Use rs.initiate() on one and only one member of the replica set" -- docs.mongodb.com/manual/tutorial/deploy-replica-set

Sudhanshu Gaur Over a year ago

hey man actually i am facing an error Error: couldn't add user: not authorized on admin to execute command. You can also find my question here stackoverflow.com/questions/41783700/… . It would be a lot much easier if you could tell me from which url(source) you have done this whole password authentication thing, please help me i have searched everywhere but didn't find anything ??

Ukor Over a year ago

To enforce authentication for existing replicate set docs.mongodb.com/manual/tutorial/…

K patel Over a year ago

This works ... trial and tested on production thanks for sharing

|

Collectives™ on Stack Overflow

MongoDB replica set with simple password authentication

1 Answer 1

6 Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

6 Comments

Linked

Related