Currently, the details of what configuration is being used are not available within the encryption callback function. This means that there's no way to access method settings or provider settings within that function. See Undefined index issues and incomplete settings for an example of how this is undesirable.

CommentFileSizeAuthor
#1 encrypt-pass-config-encrypt-callback-2371789-0.patch458 bytesrlhawk
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

rlhawk’s picture

rlhawk
Primary language English
Location Seattle, Washington, United States
CreditAttribution: rlhawk commented
Status: Active » Needs review
FileSize
encrypt-pass-config-encrypt-callback-2371789-0.patch458 bytes

The easiest way to do this is to include the configuration in the $options argument when calling the encryption callback function. Then the implementing module can access settings as needed. Here's a patch that does that.

Cellar Door’s picture

Cellar Door CreditAttribution: Cellar Door commented
Status: Needs review » Reviewed & tested by the community

This looks like a simple one-liner that will allow for encryption methods to know about the new config settings. I don't see it causing any issues and the patch works well so I'm marking RTBC so we can get it into dev for everyone.

  • rlhawk committed 3100f93 on 7.x-2.x 
    Issue #2371789 by rlhawk, Cellar Door: Make configuration available in...
rlhawk’s picture

rlhawk
Primary language English
Location Seattle, Washington, United States
CreditAttribution: rlhawk commented
Status: Reviewed & tested by the community » Fixed

Marking as fixed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.