[SERVER-19721] Restore authSchemaUpgrade command Created: 03/Aug/15 Updated: 30/Oct/15 Resolved: 08/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | Andreas Nilsson |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Security 8 08/28/15, Security 9 (09/18/15) | ||||||||
| Participants: | |||||||||
| Description |
|
authSchemaUpgrade will be required in 3.2 to keep the MONGODB-CR to SCRAM-SHA-1 upgrade path open. |
| Comments |
| Comment by Githook User [ 08/Sep/15 ] |
|
Author: {u'username': u'agralius', u'name': u'Andreas Nilsson', u'email': u'andreas.nilsson@10gen.com'}Message: Fixed mongos rebase error for catalogManager(txn) |
| Comment by Andreas Nilsson [ 08/Sep/15 ] |
|
We should review that the documentation for authSchemaUpgrade for 3.0 is still relevant and does not mention 2.6 specifically. Retaining this command is simply a fallback if someone does not upgrade properly. |