[SERVER-30194] During featureCompatibilityVersion downgrade to 3.4, ensure no users or roles possess authenticationRestrictions Created: 17/Jul/17 Updated: 14/Aug/17 Resolved: 14/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | ADAM Martin (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Platforms 2017-07-31, Platforms 2017-08-21 |
| Participants: |
| Description |
|
Old nodes will be unable to process the new authenticationRestrictions field. New nodes preparing to downgrade will run {setFeatureCompatibilityVersion: "3.4"}. We should, while downgrading the featureCompatibilityVersion, ensure that no user or role possesses either an authenticationRestrictions field, or a restriction which the old node will not understand. |