Skip to content

Queryable Encryption Support #4185

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
ashni-mehta opened this issue Sep 27, 2022 · 7 comments
Closed

Queryable Encryption Support #4185

ashni-mehta opened this issue Sep 27, 2022 · 7 comments
Labels
status: feedback-provided Feedback has been provided

Comments

@ashni-mehta
Copy link
Contributor

Queryable Encryption is a new feature in MongoDB 6.0. It allows customers to encrypt sensitive data from the client side, store it as fully randomized encrypted data on the database server side, and run expressive queries on the encrypted data.

More details on Queryable Encryption here: https://www.mongodb.com/docs/manual/core/queryable-encryption/

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Sep 27, 2022
@jyemin
Copy link
Contributor

jyemin commented Sep 27, 2022

This is the part that describes the requirements for the JSON schema: https://www.mongodb.com/docs/manual/core/queryable-encryption/tutorials/aws/aws-automatic/#create-your-encrypted-collection

@christophstrobl
Copy link
Member

The missing bit seems to be the queries part. So far only queryType: "equality" and queryType: "none" are mentioned in the docs. Will there be more or a change to the format? Which boils down to if a single attribute on @Encrypted (like below) is sufficient and future proof?

@Encrypted(query = EQUALITY)

@ashni-mehta
Copy link
Contributor Author

My understanding is that more are coming in the future. I can find out if format will remain consistent.

@christophstrobl christophstrobl added status: waiting-for-feedback We need additional information before we can continue and removed status: waiting-for-triage An issue we've not yet triaged labels Oct 4, 2022
@spring-projects-issues
Copy link

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

@spring-projects-issues spring-projects-issues added the status: feedback-reminder We've sent a reminder that we need additional information before we can continue label Oct 11, 2022
@ashni-mehta
Copy link
Contributor Author

Hey, spoke to the team.

  • There will be more query types and the different query types will have different parameters at set up.
  • The persisted data format is unique per index type (ex: an index that supports "equality" cannot support range.

@spring-projects-issues spring-projects-issues added status: feedback-provided Feedback has been provided and removed status: waiting-for-feedback We need additional information before we can continue status: feedback-reminder We've sent a reminder that we need additional information before we can continue labels Oct 18, 2022
@christophstrobl
Copy link
Member

Thank you Thank you @ashni-mongodb. When using queryable encryption along with explicit encryption is the queryType only to be set when encrypting parts of the filter query or is it also allowed/required when encrypting field data for the document to store. Javadoc of EncryptOptions is a bit thin there.

@joelodom
Copy link

joelodom commented Jul 2, 2024

@christophstrobl, queryType is used when creating the encrypted collection and it's also used when creating the query filter for the find. queryType is not used when creating the payload to insert.

@ashni-mongodb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: feedback-provided Feedback has been provided
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants