[DOCS-6380] Clarify recommendations on "burn-in" period for auth schema upgrades Created: 15/Oct/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: mongodb-2.6, mongodb-3.0
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Stennie Steneker (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769

 Description   

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



 Comments   
Comment by Education Bot [ 01/Nov/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 07:52:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.