[DOCS-7958] Comment on: "manual/release-notes/3.2-downgrade.txt" Created: 25/May/16 Updated: 03/Nov/17 Resolved: 13/Jun/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dharshan Rangegowda | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: https://docs.mongodb.com/manual/release-notes/3.2-downgrade/ |
||
| Participants: | |
| Days since reply: | 7 years, 35 weeks, 2 days ago |
| Description |
|
How do you downgrade the auth schema of the users when downgrading for m 3.2 to 2.6? |
| Comments |
| Comment by Ravind Kumar (Inactive) [ 13/Jun/16 ] |
|
Closing this ticket due to no response |
| Comment by Ravind Kumar (Inactive) [ 25/May/16 ] |
|
Hello Dharshan, Can you provide us more information with your environment and what you are attempting to do? In general, we recommend downgrading from 3.2 to 3.0 first, and then to 2.6. You can find the downgrade documentation for MongoDB 3.0 here. As far as security goes, the primary concern would be the authentication mechanism. If you are currently using SCRAM-SHA-1 as the authentication mechanism, you cannot downgrade to MongoDB2.6 without disabling authentication. You would have to re-create the users or restore from a backup. If you are still using MONGODB-CR from the previous upgrade, then you should be OK to downgrade to 2.6. Let me know if this makes sense - you may need to create a ticket in the Community Support Project for further support. If your organization has a support contract with MongoDB, please reach out to your account manager for further support. |