[SERVER-79496] Ban encryption options being provided in createCollection Created: 31/Jul/23  Updated: 29/Oct/23  Resolved: 19/Sep/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Jordi Olivares Provencio Assignee: Jordi Olivares Provencio
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by COMPASS-7231 Investigate changes in SERVER-79496: ... Closed
Documented
is documented by DOCS-16390 Investigate changes in SERVER-79496: ... Closed
Related
related to SERVER-68122 Investigate replicating the collectio... Closed
related to SERVER-72227 Investigate how ESE WiredTiger config... Closed
is related to SERVER-81779 Investigate whether to sanitize colle... Closed
Assigned Teams:
Storage Execution
Backwards Compatibility: Minor Change
Sprint: Execution EMEA Team 2023-09-18, Execution EMEA Team 2023-10-02
Participants:
Linked BF Score: 35

 Description   

In SERVER-72227 we came to the conclusion that in some cases there can be situations where a collection is mistakenly created with encryption options in the config string. This can happen if an external tool makes a backup and saves the creation string as read from collStats.

These options are ephemeral in nature and should never be inserted into the durable catalog. We should consider banning them from the set of valid user options.



 Comments   
Comment by Githook User [ 19/Sep/23 ]

Author:

{'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}

Message: SERVER-79496 Ban encryption options from createCollection
Branch: master
https://github.com/mongodb/mongo/commit/627bd4597df574c5289870a3b6fbc5118f2519a7

Generated at Thu Feb 08 06:41:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.