Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
*Location*: https://docs.mongodb.org/manual/core/authentication/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36
*Referrer*: https://docs.mongodb.org/manual/tutorial/add-user-administrator/
*Screen Resolution*: 1680 x 1050
*repo*: docs
*source*: core/authentication
*Location*: https://docs.mongodb.org/manual/core/authentication/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36 *Referrer*: https://docs.mongodb.org/manual/tutorial/add-user-administrator/ *Screen Resolution*: 1680 x 1050 *repo*: docs *source*: core/authentication
Description
I just want to get going on using mongo within an application.
That means I want to configure the application with a username and password and tell it which collection etc to access.
I really do not understand why I need to understand your whole !@#$!# security model to do this.
Why do you not have a quick setup instructions that actually tells new developers how to do the setup that they need to.. given that 98% of time, they just want to be able to get a user who can read/write/restore data on just one collection..
I am having to read 10 documents on 3 different versions of mongo to just get things started.
Your application would have much much much much much much better adoption if you actually test the first hour with a new developer who just wants to get going.
Why are you wasting my time. DONT MAKE ME LEARN EVERYTHING TO DO ANYTHING.
-ft