Provide a way to encrypt users if module is enabled via config import

Created on 25 January 2023, over 2 years ago

Problem/Motivation

After #3257640: Respect is_syncing in hook_install , if the module is enabled via config import the user emails will remain unencrypted in the database. The reason for disabling the profile encryption during configuration import is that it is not really the correct time to spend a few minutes changing the database. However, this

Steps to reproduce

Enable the module by adding the module to the core.extension.yml file. Check that users remain unencrypted.

Proposed resolution

Provide a warning on the status report that emails have not yet been encrypted. Provide a mechanism to encrypt these emails using a batch operation as it might be necessary to do this for thousands of users.

Feature request
Status

Active

Version

3.0

Component

Code

Created by

🇵🇹Portugal jcnventura

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @jcnventura
  • Assigned to thedut
  • 🇫🇷France thedut

    Hello jcnventura,

    Yes we need to solve this issue.
    Anyway : if the dbee module is enabled via config import, the status report page does alert, returning an error.
    The mechanism to encrypt these emails using a batch operation does exist to but not easy to find or execute from the UI : simply saving the Dbee encryption key or uninstall-reinstall the dbee module.
    I need to dig on this issue. I keep it open.

    • thedut committed 9e4bebae on 4.x
      Issue #3336435 by thedut, jcnventura : Encryption on config import.
      
  • 🇫🇷France thedut

    Fixed into the 3.1.0-rc2 relaese

  • Now that this issue is closed, please review the contribution record.

    As a contributor, attribute any organization helped you, or if you volunteered your own time.

    Maintainers, please credit people who helped resolve this issue.

Production build 0.71.5 2024