-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.0.2
-
Component/s: Security
-
None
-
ALL
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
while profile level is 2, auth using a user not exists in the db will lost connection. and this problem still exists in current 2.1.0 version.
$ ./mongo
MongoDB shell version: 2.0.2
connecting to: test
> use admin
switched to db admin
> db.auth('admin','.....')
1
> use test2
switched to db test2
> db.getProfiling
db.getProfilingLevel( db.getProfilingStatus(
> db.getProfilingLevel()
0
> db.setProfilingLevel(2)
>
bye
$ ./mongo
MongoDB shell version: 2.0.2
connecting to: test
> use test2
switched to db test2
> db.auth('aa','aa')
Tue Feb 28 15:34:15 DBClientCursor::init call() failed
Tue Feb 28 15:34:15 query failed : test2.$cmd
to: 127.0.0.1
Tue Feb 28 15:34:15 Error: error doing query: failed shell/
collection.js:151
Tue Feb 28 15:34:15 trying reconnect to 127.0.0.1
Tue Feb 28 15:34:15 reconnect 127.0.0.1 ok
- duplicates
-
SERVER-5033 Database with auth turned on and profile = 2 on the command line does not allow "show dbs" to be run from driver
-
- Closed
-