Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
None
-
windows, mongo 3.2.0
*Location*: https://docs.mongodb.org/manual/tutorial/enable-authentication/
*User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.80 Safari/537.36
*Referrer*: http://stackoverflow.com/questions/16034373/mongodb-2-4-replica-set-with-authorization
*Screen Resolution*: 1280 x 1024
*repo*: docs
*source*: tutorial/enable-authentication
windows, mongo 3.2.0 *Location*: https://docs.mongodb.org/manual/tutorial/enable-authentication/ *User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.80 Safari/537.36 *Referrer*: http://stackoverflow.com/questions/16034373/mongodb-2-4-replica-set-with-authorization *Screen Resolution*: 1280 x 1024 *repo*: docs *source*: tutorial/enable-authentication
Description
It does not tell that if client auth is enabled on a replica set, then we need to use at least a key file for the replica set nodes to do internal authentication, otherwise the secondaries never can connect and all nodes stuck in recovering mode until internal auth is fixed