Hi,

I have just been informed of the following by ANZ:

================

MasterCard Payment Gateway Services is ANZ’s technology provider for ANZ eGateTM. MasterCard has advised ANZ that the MD5 algorithms – a security algorithm used in ANZ eGateTM will not be accepted after 30 November 2016. Merchants using the MD5 algorithm will need to upgrade to SHA256 algorithms by 30 November 2016.

This change is part of a security update from MasterCard to maintain appropriate levels of safety, security and integrity to your business and your customers.

===================

Is this module likely to updated soon to compliment the required changes?

CommentFileSizeAuthor
#10 2824813.patch5.97 KBlomasr

Comments

tj99ay created an issue. See original summary.

tripper54’s picture

tripper54 commented

As I'm no longer involved in any sites that use this module, I won't be making any changes. I'd be happy to review patches.

danuddara’s picture

danuddara commented

I don't see any MD5 hashing algorithm has been used in this module. Did anyone test it with the Test merchant ID?

You can do a test with your TEST merchant id. if the order goes through. that means it works fine.
the change have been applied only to "3 Party SHA256 PHP".

I don't see any MD5 change to SHA in the "2 Party VPC_PHP".

http://www.anz.com/australia/business/merchant/zips/VirtualPaymentClientDevelopersKit.zip

This module should work without any problem.

to make sure you can call the ANZ Integrated Solutions team on 0800 473 453
between 8.30am and 4.30pm NZT Mon -Fri

janvonmulert’s picture

janvonmulert commented

HI Danuddara,

I have this module working with a test merchant id and I can confirm its functioning as expected. I am in contact with ANZ tech support and waiting on confirmation that it does not require and upgrade.

Thanks so much for your help you are a lifesaver!

danuddara’s picture

danuddara commented

That means we all are good here. The Test gateway is already upgraded to accept the SHA256 hash.
it will pop you up an error if it uses the MD5 algorithm with the Test Merchant ID.

cheers! :)

tj99ay’s picture

tj99ay commented

That's wonderful news. Thank you :-)

levon_k’s picture

levon_k commented

Guys and what about 3 party? I actually see the md5 function and looks like it should be replaced somehow.

danuddara’s picture

danuddara commented

@levon_k , where did you find the md5 code?. Is it in this module (Commerce MIGS Merchant - 7.x-1.0 ) or somewhere else?

ranelpadon’s picture

ranelpadon commented

We have a similar migration use case/requirement. It turned out that we have a custom module that extends/overrides some parts of the Commerce MIGS Merchant module. Our custom module has some md5 codes on it and we need to migrate it to SHA256 as per GlobalPay/MIGS policy.

Upon digging further in the Developer docs/guides that GlobalPay has provided and scouring the web for other related resources, eventually I made it to work by implementing a solution based on this: https://www.drupal.org/files/issues/upgradeMD5toSHA256-2825564-1.patch

lomasr’s picture

lomasr commented
StatusFileSize
new 2824813.patch5.97 KB

I have done changes for SHA 256

lomasr’s picture

lomasr commented
Status: Active » Needs review