|
The Timing sections of 2.6 & 3.0 auth schema upgrades mention a "burn-in" period without being entirely clear on the intent of this messaging (i.e. the downgrade implications if auth schema has been upgraded to a newer version):
In particular, the phrasing "Because downgrades are more difficult after you upgrade the user authentication model" should be removed and replaced with an explicit warning that there is no auth schema downgrade process as well as strong encouragement to thoroughly test major version upgrades in a staging/UAT environment prior to deploying in production.
The 3.0 upgrade does have an explicit warning later on the page which would be worth linking or repeating in the Timing section:
http://docs.mongodb.org/master/release-notes/3.0-scram/#upgrade-2-6-mongodb-cr-users-to-scram-sha-1
Also see user feedback in: https://groups.google.com/forum/?#!msg/mongodb-user/Cj-ZS-0X4T0/g5LjyHVRDQAJ
|