Skip to content

DATAMONGO-2306 - Add field level encryption to JSON Schema. #766

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 4 commits into from

Conversation

christophstrobl
Copy link
Member

We now support encrypted fields via MongoJsonSchema and allow XML configuration of com.mongodb.AutoEncryptionSettings via a dedicated factory bean.


This change builds upon MongoDB Java Driver 3.11.0-beta4 that should come in via #764.

christophstrobl and others added 3 commits July 1, 2019 14:16
We now support encrypted fields via MongoJsonSchema and allow XML configuration of com.mongodb.AutoEncryptionSettings via a dedicated factory bean.
Add Nullable annotation to nullable method args. Remove IV from JSON Schema as it is not listed in Mongo specs.

Tweak wording in docs.
@mp911de mp911de force-pushed the issue/DATAMONGO-2306 branch from e30f5f5 to 665aff4 Compare July 1, 2019 12:18
We now parse encryption-settings-ref as reference to AutoEncryptionSettings beans. Testing such a setup requires a proper crypto setup with external libraries.
mp911de pushed a commit that referenced this pull request Jul 17, 2019
We now support encrypted fields via MongoJsonSchema and allow XML configuration of com.mongodb.AutoEncryptionSettings via a dedicated factory bean.

Original pull request: #766.
mp911de added a commit that referenced this pull request Jul 17, 2019
Add Nullable annotation to nullable method args. Remove IV from JSON Schema as it is not listed in Mongo specs.

Tweak wording in docs. Parse encryption-settings-ref for MongoClientOptions. Add support for KeyId's in encrypted JSON schema properties.

Original pull request: #766.
@mp911de
Copy link
Member

mp911de commented Jul 17, 2019

That's merged and polished now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants