-
Type: Task
-
Resolution: Cannot Reproduce
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.0.37
-
Component/s: None
-
Labels:
-
Environment:Linux Redsandro 3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 09:43:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
-
Empty show more show less
I'm trying to deploy something on different machines. Some of them use auth for MongoDB, some of them don't and only listen to localhost. Most run MongoDB 2.6.11.
I used to do `mongodb.client.open` first and then `mongodb.client.authenticate` in the callback. When the authentication failed on non-auth databases, the connection would still be open, and I could see this using `mongodb.client._state === 'connected'`.
However, after a long due update to Node-MongoDB 2.0.x, there is no connection if the auth fails. On the same server. Shouldn't this be up to the server to decide?