-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Environment:64bit Amazon Linux 2015.09 v2.0.8 running Node.js
Node 4.3.0
Using mongojs 2.4.0
Mongodb driver version
-
Empty show more show less
We were recently upgraded from 2.1.19 to 2.1.21 and immediately noticed a flood of "not authorized for query" errors. These are coming from both our Mongo 3.0 and 3.2 databases hosted on Compose.io. We use the `mongojs` wrapper for `mongodb`.
We upgraded and downgraded mongodb between 2.1.19 and 2.1.21 and are very certain that this issue is caused by an update in either 2.1.20 or 2.1.21. (we haven't had time to check 2.1.20 yet).
Is this a know issue?