This is a rewrite of the mongodb part of the nosql module. It is not perfect but solves a series of authentication issues:
reactivemongo 0.11.7 had a bug that prevented to use asynchronous authentication (the successful authentication future was successful before authentication completed) this is fixed in reactivemongo 0.11.11, which, in addition, supports MongoDB 3.2
it is now possible to manage collections opened by different users (to whom different privileges are granted)
Note that it seems that, contrary to reactivemongo 0.11.7, version 0.11.11 reuses tuktu's Akka port and conflicts with it, so, it was necessary to add a dedicated section "mongo-async-driver" in application.conf to specify an alternative port.
I'll accept this for now as looking at didn't ring any alarmbells. We will be using and testing this in the near future, so things might change soon though.
Hi Erik and all,
This is a rewrite of the mongodb part of the nosql module. It is not perfect but solves a series of authentication issues:
reactivemongo 0.11.7 had a bug that prevented to use asynchronous authentication (the successful authentication future was successful before authentication completed) this is fixed in reactivemongo 0.11.11, which, in addition, supports MongoDB 3.2
it is now possible to manage collections opened by different users (to whom different privileges are granted)
Note that it seems that, contrary to reactivemongo 0.11.7, version 0.11.11 reuses tuktu's Akka port and conflicts with it, so, it was necessary to add a dedicated section "mongo-async-driver" in application.conf to specify an alternative port.
What do you think?
David