In authenticated environments, we are seeing random cursors which do not authenticate. Other cursors from the same source are authenticating properly. In the MongoDB logs, these unauthenticated cursors are not even attempting to authenticate. I've seen this 3 times over the past week, but appears to be unpredictable.

In the most recent scenario, an unauthenticated cursor occurred after a step down of the Replica Set. The cursor was connected to the server that stepped down, was previously Primary, and now a Secondary.

The following was the MongoDB log:

Thu Sep 6 16:10:55 [initandlisten] connection accepted from 10.82.11.157:39608 MONGOID-913
Thu Sep 6 16:10:55 [conn912] assertion 10057 unauthorized db:myDatabase lock type:-1 client:10.82.11.156 ns:myDatabase.users query:{ $query:

{ _id: ObjectId('4f6b0a7dcf2bee4c65000001') }

, $orderby:

{ _id: 1 }

}

The cursor lasted for 5 minutes and tried 33 queries on the "users" collection.

This issue cannot be predictably reproduced, but I wanted to put it on the issues as I've seen it a few times with a few different clients over the past week. It is happening with v3.0.5.