force base64_encode encrypted data for plugins that don't have the option

Created on 11 October 2017, over 7 years ago
Updated 29 April 2025, 16 days ago

some encryption plugins like Sodium don't base64_encode the data which causes problems when trying to put the information in teh database like with the webform_encrypt module.

I propose we alter the module to add an option for force base64 encoding/decoding independent of the plugin

πŸ› Bug report
Status

Needs work

Version

3.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States jrglasgow Idaho

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

Comments & Activities

Not all content is available!

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

  • πŸ‡¬πŸ‡§United Kingdom altcom_neil
  • πŸ‡¬πŸ‡§United Kingdom altcom_neil

    I have just run into this trying to use the latest versions of everything:

    • drupal/encrypt v3.2.0
    • drupal/webform_encrypt 2.0.0-alpha1
    • drupal/sodium 3.0.0

    There is an issue ticket all for this issue with in each of the projects with not much recent progress. See

    It seems that it would make sense to solve the issue here in Encrypt? Allowing Sodium (and any future encryption plugins) to simply return their native encrypted string would be the simplest in the long term?

    The current patch file in #18 works with the latest code.

    Tested with Drupal 10.4.3. PHP 8.3.17, MySQL 8.4.3, Webform 6.2.9

Production build 0.71.5 2024