Problem/Motivation
Currently, the Acquia-VWO Connect module stores VWO Account ID within the configuration, which poses security risks. The Drupal Key module provides a mechanism to manage secrets securely by storing keys outside of Drupal config (e.g., in environment variables or external files) and providing them when needed.
Proposed resolution
This module should enhance security in this module by integrating with the Drupal Key module. This integration will ensure sensitive VWO Account ID is not stored directly in the module's configuration but are instead securely retrieved via the Key module on demand.
Issue fork acquia_vwo-3562972
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
rajeshreeputra