Skip to content

Encrypted scope-specific config values fail to decrypt on PHP7 #8591

@zack6849

Description

@zack6849

It seems that scope based config fails to decrypt data on anything but the default store

We first noticed this when all of our stores apart from the default one failed to process paypal transactions. After further editing of the code so that we could actually see the username and password information being sent to paypal, we discovered the username field is blank, and the password field is garbled garbage data, which leads me to assume it's failed decryption.

I thought it might've just been leaving it encrypted, so i edited the code and told it to decrypt the already supposedly decrypted value, to no avail, so as of now it seems that PayPal on multi-store setups running 2.1.4 on PHP7 won't function (assuming that the PayPal account details are different than the default store, of course)

We couldn't find anything about others having this issue via google, which was quite surprising to me, so if you need any more information please don't hesitate to ask

Preconditions

  1. Magento v2.1.4
  2. PHP v7.0.6 on Ubuntu

Steps to reproduce

  1. Change PayPal password of non-default store
  2. Attempt to checkout
  3. User authentication unsuccessful

Expected result

  1. A successful transaction

Actual result

  1. The user field is blank, and the password field is garbed nonsense, from what I can only assume is a fail to decrypt (EG: c▒^`▒▒XP)

This issue feels quite similar to issues #2984 and #3305

Metadata

Metadata

Assignees

No one assigned

    Labels

    Component: PaymentEvent: distributed-cdDistributed Contribution DayFixed in 2.1.xThe issue has been fixed in 2.1 release lineFixed in 2.2.xThe issue has been fixed in 2.2 release lineIssue: Clear DescriptionGate 2 Passed. Manual verification of the issue description passedIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedIssue: Format is validGate 1 Passed. Automatic verification of issue format passedIssue: Ready for WorkGate 4. Acknowledged. Issue is added to backlog and ready for developmentReproduced on 2.1.xThe issue has been reproduced on latest 2.1 releasebug report

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions