During featureCompatibilityVersion downgrade to 3.4, ensure no users or roles possess authenticationRestrictions

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Platforms 2017-07-31, Platforms 2017-08-21
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            ADAM Martin (Inactive)
            Reporter:
            Spencer Jackson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: