Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
mongo 3.0.4 WiredTiger running on wheezy chroot on x64 machine
*Location*: http://docs.mongodb.org/manual/tutorial/enable-authentication-in-sharded-cluster/
*User-Agent*: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.99 Safari/537.36
*Referrer*: https://www.google.it/
*Screen Resolution*: 1366 x 768
*repo*: docs
*source*: tutorial/enable-authentication-in-sharded-cluster
mongo 3.0.4 WiredTiger running on wheezy chroot on x64 machine *Location*: http://docs.mongodb.org/manual/tutorial/enable-authentication-in-sharded-cluster/ *User-Agent*: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.99 Safari/537.36 *Referrer*: https://www.google.it/ *Screen Resolution*: 1366 x 768 *repo*: docs *source*: tutorial/enable-authentication-in-sharded-cluster
Description
Hi
Sorry but the instructions are not clear enough, to be more precise the step 3.
I have my configsvr, 5 shards and mongos all started wtih the same "security.keyFile: /etc/mongodb/key_file", I've managed to connect to the mongos port and created the admin user, tried different roles and combinations: root, userAdminAnyDatabase, readWritieAnyDatabase. afterwards I'm able to use this user to connect to the mongos ... but not on any of the others members/components of the cluster.
so which is the complete and correct procedure ?
should I create the "admin user" first on the mongod instances and then on the mongos ? it must be the same ? (same user + same pass) ?
Thank you for your help and time