Authorize.Net changes

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
9/1/2015 2:40:26 PM
Gravatar
Total Posts 5

Authorize.Net changes

Joe,

Our client has received notices from Authorize.Net about changes they have coming.   I believe if there are any changes required, it would be within Mojo Portal.   I'm pasting in the quote from the Authorize.Net email.   Can you please confirm that the Mojo sites will continue to operate properly with Authorize.Net with NO CHANGES NEEDED or if changes are needed, can you confirm that a Mojo update/upgrade will be available prior to 9/21?

Thanks,

Jeff
Jeff [at] 4TruthWebDesign [DOT] com

QUOTE FROM AUTHORIZE.NET

As part of our continuous upgrades to enhance system performance and security, on September 21, 2015, we are upgrading api.authorize.net to new security certificates, which are signed using Security Hash Algorithm 2 (SHA-2) and 2048-bit signatures.

These upgrades were already completed on secure.authorize.net in May. If your website or payment solution connects to api.authorize.net and any updates are necessary to use the new certificates, please refer to this blog post in our Developer Community, which has all of the certificate information you and your developer will need for this update. Our sandbox environment has already been updated so that you can validate that your solution will continue to work using SHA-2 signed certificates, prior to September 21st.

After the update is complete on September 21st, any website or payment solution that connects via api.authorize.net that cannot validate SHA-2 signed certificates will fail to connect to Authorize.Net's servers.

9/1/2015 2:46:00 PM
Gravatar
Total Posts 18444

Re: Authorize.Net changes

no changes are needed

You must sign in to post in the forums. This thread is closed to new posts.