Please post all pre-sales questions of all products on this forum
Authorize.net Discontinued TLS 1.0/1.1
- Clifton Murphy
-
Topic Author
- Offline
- Premium Member
-
Less
More
8 years 4 months ago #98587
by Clifton Murphy
Clifton Murphy - Owner
Funny Bug Bees And Wood Works
252-933-4840
Authorize.net Discontinued TLS 1.0/1.1 was created by Clifton Murphy
Is the Authorize.net payment gateway build into Eshop using TLS 1.2, because if not it will cease to function on September 18th. I got the following from authorize.net regarding changes.
Dear Authorize.net Customer
As you may be aware, new PCI DSS requirements state that all payment systems must disable early TLS by 2018. Transport Layer Security (TLS), is a technology used to encrypt sensitive information sent via the Internet. TLS is the replacement for Secure Sockets Layer (SSL).
In preparation for this requirement, Authorize.Net plans to disable TLS 1.0 and TLS 1.1 on the following dates:
Sandbox: COMPLETE
Production: September 18, 2017
We have disabled the sandbox in advance of production to allow you and your developer time to test your website or payment solution and ensure you are no longer using TLS 1.0 or 1.1 prior to September 18th.
Please contact your web developer or payment solution provider, as well as your web hosting company, to confirm that they can support TLS 1.2 for your API connections.
In addition, we plan to retire the 3DES cipher (a data encryption standard) in production soon. However, the date has not yet been finalized. We will notify you once it has.
Please refer your developer or solution provider to our API Best Practices for cipher recommendations, details about TLS 1.2 platform support, and other integration suggestions.
Note: If you are not using the current version of your web browser, please take a few moments to upgrade it now. Browsers released prior to 2014 may not support TLS 1.2. You can check your browser's TLS support by visiting www.howsmyssl.com/ .
Thank you for your attention to this matter and for being an Authorize.Net merchant.
Sincerely,
Authorize.Net
Dear Authorize.net Customer
As you may be aware, new PCI DSS requirements state that all payment systems must disable early TLS by 2018. Transport Layer Security (TLS), is a technology used to encrypt sensitive information sent via the Internet. TLS is the replacement for Secure Sockets Layer (SSL).
In preparation for this requirement, Authorize.Net plans to disable TLS 1.0 and TLS 1.1 on the following dates:
Sandbox: COMPLETE
Production: September 18, 2017
We have disabled the sandbox in advance of production to allow you and your developer time to test your website or payment solution and ensure you are no longer using TLS 1.0 or 1.1 prior to September 18th.
Please contact your web developer or payment solution provider, as well as your web hosting company, to confirm that they can support TLS 1.2 for your API connections.
In addition, we plan to retire the 3DES cipher (a data encryption standard) in production soon. However, the date has not yet been finalized. We will notify you once it has.
Please refer your developer or solution provider to our API Best Practices for cipher recommendations, details about TLS 1.2 platform support, and other integration suggestions.
Note: If you are not using the current version of your web browser, please take a few moments to upgrade it now. Browsers released prior to 2014 may not support TLS 1.2. You can check your browser's TLS support by visiting www.howsmyssl.com/ .
Thank you for your attention to this matter and for being an Authorize.Net merchant.
Sincerely,
Authorize.Net
Clifton Murphy - Owner
Funny Bug Bees And Wood Works
252-933-4840
Please Log in or Create an account to join the conversation.
- Robert Jacobi
- Offline
- New Member
-
Less
More
- Posts: 5
- Thank you received: 0
8 years 1 month ago #101739
by Robert Jacobi
Replied by Robert Jacobi on topic Authorize.net Discontinued TLS 1.0/1.1
Authorize.net just pushed the requirement until 2018 but that doesn't solve the problem. Just tried in the sandbox and appears that TLS 1.2 is not supported for authorize.net - can someone please confirm? Using Joom Donation with authorize plugin. Thank you.
Please Log in or Create an account to join the conversation.
- Tuan Pham Ngoc
- Offline
- Administrator
-
8 years 1 month ago #101740
by Tuan Pham Ngoc
Replied by Tuan Pham Ngoc on topic Authorize.net Discontinued TLS 1.0/1.1
Hi Robert
At the moment, our extensions don't support TLS 1.2 for Authorize.net yet. Something we can work on and make it ready next week
I just implemented the change, tested and it worked well (I can only test it in test mode as I don't have a live authorize.net account)
Could you please get this updated library, go to Extensions -> Manager, install it, then test it again and update us with the result?
Regards,
Tuan
At the moment, our extensions don't support TLS 1.2 for Authorize.net yet. Something we can work on and make it ready next week
I just implemented the change, tested and it worked well (I can only test it in test mode as I don't have a live authorize.net account)
Could you please get this updated library, go to Extensions -> Manager, install it, then test it again and update us with the result?
Regards,
Tuan
- Robert Jacobi
- Offline
- New Member
-
Less
More
- Posts: 5
- Thank you received: 0
8 years 1 month ago - 8 years 1 month ago #101799
by Robert Jacobi
Replied by Robert Jacobi on topic Authorize.net Discontinued TLS 1.0/1.1
I will review the new library this weekend and provide feedback. Thank you.
Last edit: 8 years 1 month ago by Robert Jacobi.
Please Log in or Create an account to join the conversation.
- Tuan Pham Ngoc
- Offline
- Administrator
-
8 years 1 month ago #101806
by Tuan Pham Ngoc
Replied by Tuan Pham Ngoc on topic Authorize.net Discontinued TLS 1.0/1.1
Great. Thanks Robert
Please Log in or Create an account to join the conversation.
- Clifton Murphy
-
Topic Author
- Offline
- Premium Member
-
8 years 1 month ago #101813
by Clifton Murphy
Clifton Murphy - Owner
Funny Bug Bees And Wood Works
252-933-4840
Replied by Clifton Murphy on topic Authorize.net Discontinued TLS 1.0/1.1
is this library for Eshop, since that is what i started this topic on im guessing it is, but can you verify? Does this library need to be installed on all Eshop installations using Authorize.net as a payment gateway?
Clifton Murphy - Owner
Funny Bug Bees And Wood Works
252-933-4840
Please Log in or Create an account to join the conversation.
- Tuan Pham Ngoc
- Offline
- Administrator
-
8 years 1 month ago #101815
by Tuan Pham Ngoc
Replied by Tuan Pham Ngoc on topic Authorize.net Discontinued TLS 1.0/1.1
Hi Clifton
Yes. The library can be used for Eshop, too. It is used in all of our extensions. Maybe you should wait for few more days, once we have Robert confirm that it works, we will update all our extensions with this change (hopefully, beginning of next week)
Regards,
Tuan
Yes. The library can be used for Eshop, too. It is used in all of our extensions. Maybe you should wait for few more days, once we have Robert confirm that it works, we will update all our extensions with this change (hopefully, beginning of next week)
Regards,
Tuan
Please Log in or Create an account to join the conversation.
- Robert Jacobi
- Offline
- New Member
-
Less
More
- Posts: 5
- Thank you received: 0
8 years 1 month ago #101981
by Robert Jacobi
Replied by Robert Jacobi on topic Authorize.net Discontinued TLS 1.0/1.1
We tested the library on production in the plugins test mode (which should be connecting us to the TLS 1.2 sandbox exclusively). We were not able to "login." You should be able to create a free sandbox account and test on your end since the authorize.net sandbox is only accepting TLS 1.2.
Please Log in or Create an account to join the conversation.
- Tuan Pham Ngoc
- Offline
- Administrator
-
8 years 1 month ago #101996
by Tuan Pham Ngoc
Replied by Tuan Pham Ngoc on topic Authorize.net Discontinued TLS 1.0/1.1
Hi Robert
Could you please explain more details? For Authorize.net (AIM method), users just enter credit card information directly on your site for processing payment, so I don't understand why you need to "login"? Could you please give us more information about it?
Tuan
Could you please explain more details? For Authorize.net (AIM method), users just enter credit card information directly on your site for processing payment, so I don't understand why you need to "login"? Could you please give us more information about it?
Tuan
Please Log in or Create an account to join the conversation.
- Robert Jacobi
- Offline
- New Member
-
Less
More
- Posts: 5
- Thank you received: 0
8 years 1 month ago #102067
by Robert Jacobi
Replied by Robert Jacobi on topic Authorize.net Discontinued TLS 1.0/1.1
We are not able to authenticate to the gateway, which I assume is an issue with TLS 1.2 in the sandbox. For payment processing we redirect to the sandbox link:
test.authorize.net/gateway/transact.dll
And get the following error message:
The following errors have occurred.
(13) The merchant login ID or password is invalid or the account is inactive.
Note: This is not an issue when we point to the live transaction link (whether authorize is in Test or Live mode).
test.authorize.net/gateway/transact.dll
And get the following error message:
The following errors have occurred.
(13) The merchant login ID or password is invalid or the account is inactive.
Note: This is not an issue when we point to the live transaction link (whether authorize is in Test or Live mode).
Please Log in or Create an account to join the conversation.
Moderators: Tuan Pham Ngoc, Giang Dinh Truong, Dang Thuc Dam
Support
Documentation
Information
Copyright © 2025 Joomla Extensions by Joomdonation. All Rights Reserved.
joomdonation.com is not affiliated with or endorsed by the Joomla! Project or Open Source Matters.
The Joomla! name and logo is used under a limited license granted by Open Source Matters the trademark holder in the United States and other countries.
The Joomla! name and logo is used under a limited license granted by Open Source Matters the trademark holder in the United States and other countries.