-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CECAbank: Update encryption to SHA2 #3278
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. After updating core to this new AM release, we should keep an eye on Lava (https://lava.spreedly.com/gateways/cecabank/organizations/month/2019/7) to sanity check that Cecabank transactions are still going through, since the production URL has changed.
Good point on monitoring Lava when deploying. Get familiar with how to roll forward just in case 😄 |
Updated the encryption method for the CECAbank gateway from SHA1 to SHA2. This change also included updating the URLs for the gateway and revising the remote tests to work with the new URL. CE-23 Unit: 7 tests, 36 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 100% passed Remote: 5 tests, 17 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 100% passed
332d14e
to
374a82c
Compare
Updated the encryption method for the CECAbank gateway from SHA1 to
SHA2. This change also included updating the URLs for the gateway and
revising the remote tests.
CE-23
Unit:
7 tests, 36 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions,
0 notifications
100% passed
Remote:
5 tests, 17 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions,
0 notifications
100% passed