Allow keyAltName in encryptedFieldsMap

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • 1.17.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Not Needed
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      It would be a good UX improvement to allow keyAltName in the encryptedFieldsMap instead of always requiring {{keyId}}s, and reduce the effort to get started with QE since it avoids the chicken-and-egg problem where users first need to create the keys using a half-autoencryption-configured MongoClient before being able to create the main MongoClient instance.

      Since this work can probably be done entirely client-side, libmongocrypt seems like a good starting point.

            Assignee:
            Adrian Dole
            Reporter:
            Anna Henningsen
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: