Optional field encryption

[mxstbr]

Describe the feature you'd like

It would be awesome if one could encrypt certain fields (or columns) at the db level automatically. For example:

type User {
  id: ID! @unique
  email: String! @encrypt
}

All emails would now be encrypted with a globally configured key in the database, making it harder for a potential hacker to get the list of emails of our users.

Postgres has a db-level feature that allows this (https://www.postgresql.org/docs/8.1/encryption-options.html), but I don't know about other databases.

Describe alternatives you've considered

• One could handle this in the application layer, but that's tedious and error-prone. It'd be much nicer if Prisma handled this out of the box

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.

[JonnyBGod]

This would be much needed feature to store passwords on the database.

[codeincontext]

Ping. We also want this (not for storing passwords in the database though!)

[johhansantana]

This would work great for handling PII and other compliance stuff.

[Fabiomad85]

i thik its useful

[athyuttamre]

Also interested in this! My use case is that I'm building an API based product and want to store the API keys I issue in the database. Encrypting this data would make it a bit safer in case the database gets leaked.