Document how to limit encryption/decryption to specific entity bundles

Created on 29 September 2022, over 1 year ago

Updated 9 February 2023, over 1 year ago

Currently, if you enable encryption for a user-defined field or a base field, all instances of that field on all content types are encrypted.

However, in some use cases, there may be a field that is sensitive on one bundle but not others.

For example, a site could have several taxonomy vocabularies, but only one vocabulary has a sensitive title field.

So, it would be great if there was a way to limit field encryption to specific entity bundles.

🐛 Bug report

Status

Fixed

Version

3.1

Component

Documentation

Created by

🇯🇵Japan ptmkenny

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

alexpott → committed 70829b8a on 3.1.x

Issue #3312553 by ptmkenny, alexpott: Document how to limit encryption/...

Status changed to Fixed over 1 year ago3:47pm 9 February 2023
Comment over 1 year ago →
🇬🇧United Kingdom alexpott 🇪🇺🌍
I fixed up the README to be a little less Drupal version specific. Thanks @ptmkenny for the additions to the README nice.
Comment over 1 year ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.69.0 2024