Fix validation of encrypted field paths during create collection

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Security 2022-04-18
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The validation in collection_options_validation.cpp of each encrypted field path in the encryptedFieldConfig rejects commands where a field name is a prefix of another (e.g. "foo" and "foobar"). However, it should be rejecting a field path only if it is a dotted prefix of another (e.g. "foo" and "foo.bar").

            Assignee:
            Erwin Pe
            Reporter:
            Erwin Pe
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: