Yes, it is the same. In my case the database already had some users configured. But because I did't start the server with --auth option, MongoDB ignored all users and allowed everyone to connect.
An solution for the people like me, that forget the --auth would be: Situation #1, new database: Start MongoDb without any users, but as soon as the admin user is added, drop all connections and enable authentication…
- Why should it be disabled by default? I don't agree it should, but understand why it is disabled by default: for easy and quick start of development on the local machine.
I also have been affected by the same "hack". Turns out I have simply forgot to start mongod with --auth option, even through the I had created users for different databases, including the admin! Looks like in "non…
Yes, it is the same. In my case the database already had some users configured. But because I did't start the server with --auth option, MongoDB ignored all users and allowed everyone to connect.
An solution for the people like me, that forget the --auth would be: Situation #1, new database: Start MongoDb without any users, but as soon as the admin user is added, drop all connections and enable authentication…
- Why should it be disabled by default? I don't agree it should, but understand why it is disabled by default: for easy and quick start of development on the local machine.
I also have been affected by the same "hack". Turns out I have simply forgot to start mongod with --auth option, even through the I had created users for different databases, including the admin! Looks like in "non…