-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.9.0
-
Component/s: Connection Management
-
Environment:MongoDB v2.2.0 (replica set with authentication turned on)
MongoDB Java Driver v2.9.0
When MapReduce command outputs to a temp DB, it will fail due to unauthorization error. This is because the output DB of MapReduce is not the same as the one I issue the MapReduce command on, DBPort will not be able to authenticate against the output DB.
I've figured out a workaround that I have to add a method to DB class to enforce authentication, such that before sending out the MapReduce command, I can ensure my temp DB is authenticated for that connection. But this is not ideal, as the client shouldn't need to deal with all these complexities.
- duplicates
-
JAVA-691 Authentication enhancements
- Closed
- is related to
-
SERVER-7155 Problem with authentication of connections used for mapReduce when writing to an output collection
- Closed