-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: manual
-
Labels:
-
Environment:Ubuntu Linux x64
*Location*: http://docs.mongodb.org/manual/tutorial/enable-authentication/
*User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/core/authentication/
*Screen Resolution*: 1280 x 1024
*repo*: docs
*source*: tutorial/enable-authentication
Ubuntu Linux x64 *Location*: http://docs.mongodb.org/manual/tutorial/enable-authentication/ *User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/core/authentication/ *Screen Resolution*: 1280 x 1024 *repo*: docs *source*: tutorial/enable-authentication
When following the procedure described here, the mongo shell reports the following error on startup:
Error while trying to show server startup warnings: not authorized on admin to execute command
{ getLog: "startupWarnings" }I expect that this is because the userAdminAnyDatabase role has restrictions on executing commands, but the appearance of this message made me think that I had done something wrong (and I've seen a couple messages on StackOverflow that indicate that others have the same thought). A clearer explanation that userAdminAnyDatabase has user-related privileges only and that the warning is expected would probably save people some time.