Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
None
-
Mongo 2.4 authentication schema with Mongo 2.6 runtime on it.
*Location*: http://docs.mongodb.org/manual/release-notes/2.6-upgrade-authorization/#upgrade-authorization-model
*User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/release-notes/2.6-upgrade/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: release-notes/2.6-upgrade-authorization
Mongo 2.4 authentication schema with Mongo 2.6 runtime on it. *Location*: http://docs.mongodb.org/manual/release-notes/2.6-upgrade-authorization/#upgrade-authorization-model *User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/release-notes/2.6-upgrade/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: release-notes/2.6-upgrade-authorization
Description
There is no way to meet the requirements given at the start of the upgrade procedure. One cannot have or create a user with any roles and specifically not the one required.