|
Brandon Gannon
|
June 8, 2016 at 1:53 pm
Hi,
I’m following up on the thread below. Lorenzo indicated “We are introducing an option for event organizers to switch to the updated URL for Akamai shortly and you’ll be able to one-click update to access this option.”
We’d like to make sure this is taken care of before the end of this month as that is when Authorize.net will be using Akami.
Any update on this?
https://eventespresso.com/topic/authorize-net-technical-updates-2/
|
|
Josh
|
June 8, 2016 at 2:17 pm
No updates. And you should know that the option isn’t required anyway. Authorize.net will redirect to akamai automatically.
|
|
Brandon Gannon
|
June 8, 2016 at 2:32 pm
Hi Josh,
Okay, thank you. So just to be clear, there’s nothing that needs to be done on our end? Or on your end?
Brandon
|
|
Josh
|
June 8, 2016 at 3:10 pm
Here’s the thing about the Akamai option that Lorenzo mentioned:
It’s for testing and verification. So for example, if right now, you have a firewall that somehow blacklists traffic from Akamai, you wouldn’t necessarily know this until Authorize.net makes the switch. The option will let you preemptively switch to Akamai before Authorize.net does. So you could switch the option to make it go to Akamai, see that the payment response doesn’t work anymore, then check to see if your firewall (or something else on the server side) isn’t allowing Akamai to communicate to your server.
You can actually check with your host right now (or check your firewall) and make sure nothing is blocking Akamai.
|
|
Brandon Gannon
|
June 8, 2016 at 4:08 pm
Thanks Josh. Yes, I understand it’s for testing only, but Authorize.net does suggest we test during “Phase 1” (which is now through June 29) before “Phase 2” which goes into affect June 30th. As it stands, I wouldn’t know how to test that option if we chose to do so. Lorezno indicated that you guys would provide the option to the updated URL for Akamai, but I don’t see where to do that in the EE4 system. FYI, we’d prefer to test next the option next week if possible.
In the meantime, I’ll check with our web host to make sure nothing is blocking Akamai. Thanks again.
|
|
Josh
|
June 9, 2016 at 8:45 am
I don’t see where to do that in the EE4 system
You’ll find it in Event Espresso > Payment Methods > Authorize.Net AIM. It’s the option labeled: Server.
|
|
Brandon Gannon
|
June 22, 2016 at 5:39 pm
Thanks Josh. I wasn’t able to locate the option labeled “Server” that you referred to, but our web hosting company replied to me. Here is their reply:
“Besides blocking common or known malicious 3rd party IPs, our firewall by default will not block outgoing connections unless we have determined they have previously done something malicious. If you or Authorize.net have determined an IP may be blocked, please provide us the specific IP that you believe to be blocked so we can check on that. Unfortunately there is no way to permanently WhiteList an IP.”
Based upon their answer it would appear all should transition smoothly. We simply want to avoid any bumps of course.
Thank you,
Brandon
|
|
Tony
|
June 23, 2016 at 3:56 am
I wasn’t able to locate the option labeled “Server” that you referred to
Which version of Event Espresso are you using?
The ‘Server’ option was added within 4.8.42 – http://take.ms/BBgOO
Based upon their answer it would appear all should transition smoothly. We simply want to avoid any bumps of course.
It does appear that you should have no problems with the switch, most users should not have issues but it is recommend to check whilst you have the option too to save a panic on the changeover day.
|
|
Brandon Gannon
|
June 23, 2016 at 11:23 am
Hi,
Thank you for the reply. It appears we are running Event Espresso – 4.8.31.p. I’ll work with our webmaster to update to 4.8.42.
Thank you,
Brandon
|
