Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Done
-
2.1.2
-
None
-
ALL
Description
The issue here is that DBClientReplicaSet keeps an internal auth table when a user logs in, but does not attempt to remove entries when user logs out. And it uses this auth information to authenticate all new connections it creates. Note that a new connection gets created whenever an exception happened over that connection, so the same problem also occurs when the mongod node restarts after logging out.
Attachments
Issue Links
- duplicates
-
SERVER-6330 Can still perform unauthenticated queries after logging out on a replica set connection
-
- Closed
-
- is related to
-
SERVER-6117 SlaveOk Query fails with auth error even after logging in
-
- Closed
-