[DRIVERS-929] Schema map should be specifiable as file path Created: 09/Mar/20  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Drivers
Component/s: Client Side Encryption
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Oleg Pudeyev (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Issue split
split to RUBY-2997 Schema map should be specifiable as f... Closed
Related
related to DRIVERS-927 Use strings for master and data key ids Closed
related to MONGOID-5319 Permit driver FLE configuration to be... Closed
Driver Compliance:
Key Status/Resolution FixVersion
RUBY-2997 Fixed 2.18.0

 Description   

The CSE specification in https://github.com/mongodb/specifications/blob/master/source/client-side-encryption/client-side-encryption.rst#mongoclient-changes requires that MongoClient accepts schema map as an inline map.

Given the expected size of schema maps, which the CSE specification already mentions, it is likely that schema maps will be stored in their own files. Therefore it will be convenient for users to be able to specify path to the schema map rather than load the schema map and pass it inline to MongoClient.

Another instance where files are used are TLS keys and certificates. These are externally generated and are passed without modification by MongoClient to the TLS layer that uses them. Schema maps follow the same pattern of use - they are generated externally to MongoClient and MongoClient passes their contents verbatim to libmongocrypt.



 Comments   
Comment by James Kovacs [ 19/May/22 ]

This is being implemented specifically for Ruby/Mongoid in RUBY-2997. Please re-open this ticket and comment if cross-driver support for this feature is needed.

Comment by Alexander Golin (Inactive) [ 28/May/20 ]

Closing as part of backlog cleanup, please see Jeff's comment above for justification.

Generated at Thu Feb 08 08:22:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.