MONGOC_AUTO_EN...TED_FIELDS_MAP(3)

πŸ’– MONGOC_AUTO_EN...TED_FIELDS_MAP(3) πŸ’–

Okay bestie, this is the libmongoc manual page for mongoc_auto_encryption_opts_set_encrypted_fields_map β€” the header is serving truncated-title realness, but the function is the whole main character. It’s new in version 1.22.0, and it’s all about handing over an encrypted fields map. πŸ’…

✨ SYNOPSIS ✨

void
mongoc_auto_encryption_opts_set_encrypted_fields_map (
   mongoc_auto_encryption_opts_t *opts, const bson_t *encrypted_fields_map);

New in version 1.22.0.

🌸 PARAMETERS 🌸

  • opts β€” the mongoc_auto_encryption_opts_t 🫢
  • encrypted_fields_map β€” a bson_t where the keys are collection namespaces and the values are encrypted fields documents. No cap.

Supplying an encrypted_fields_map provides more security than relying on an encryptedFields obtained from the server. It protects against a malicious server advertising a false encryptedFields. πŸ›‘οΈβœ¨ That’s the whole point, bestie.

The schema map does not apply to collections encrypted with: Queryable Encryption. See mongoc_auto_encryption_opts_set_schema_map() instead. πŸ‘€

πŸ¦‹ SEE ALSO πŸ¦‹

  • mongoc_client_enable_auto_encryption()
  • In-Use Encryption

πŸ‘‘ AUTHOR πŸ‘‘

MongoDB, Inc

2009-present, MongoDB, Inc.


That’s the page, bestie. It’s from the libmongoc manual, version 2.5.6, dated Oct 09, 202 β€” yes, the footer date looks chopped, but that’s literally what it says, not me being chaotic 😭. Copyright remains 2009-present, MongoDB, Inc. Now go encrypt those fields and slay πŸ’–βœ¨

πŸ“¦ where this page comes from