|
Theodore Salamone
|
April 13, 2016 at 9:31 am
I keep getting notices that Authorize.net has moved to akamai service and that my Authorize.net information needs to be changed in EE to make it compatible – yet there is no way that I can see to make the needed changes. Please help if you have solved the problem or have suggestions.
|
|
Lorenzo Orlando Caum
|
April 13, 2016 at 10:13 am
Hi there Theodore,
We also receive those notifications from various payment processors. It sounds like this specific notification is saying that there may be an issue with the setup on your account or does it appear to be a generic email?
Could you copy and paste it here so we can share feedback?
You can also paste it into a gist and then share a link here:
https://gist.github.com
Thanks
—
Lorenzo
|
|
Theodore Salamone
|
April 20, 2016 at 5:52 am
Lorenzo, here is the notice, sent to me specifically. I have removed my gateway ID number. Please help / fix.
Authorize.Net Technical Updates Reminder
Inbox
x
Authorize.Net <no-reply@mail.authorize.net>
Mar 21
to ted
Trouble viewing this email? View it in your browser.
Authorize.Net
Authorize.Net Technical Updates
Your Payment Gateway ID:
Dear Authorize.Net Merchant:
Over the next few months, we are making several updates to our systems that you need to be aware of. They are all technical in nature and may require the assistance of your web developer or shopping cart/payment solution provider.
Please read this email carefully, and if you need to find a web developer to help you, please check out our Certified Developer Directory at http://www.authorize.net/cdd.
Akamai SureRoute Reminder
As we get further into 2016, we want to remind you of our previously announced Akamai SureRoute implementation plan and timelines. Using Akamai’s technology will help safeguard against interruptions caused by issues beyond our direct control, such as Internet congestion, fiber cable cuts and other similar issues.
If you have not already, please review the announcement and the Akamai FAQs to determine what action you should take for your particular solution. If your solution uses a firewall, please pay particular attention to this section of the FAQs to make sure you avoid any disruptions to your transaction processing.
Transaction and Batch ID Reminder
In the coming weeks, due to system updates, it will be possible to receive Authorize.Net IDs (Transaction ID, Batch ID, etc.) that are not in sequential order.
For example, currently, if you receive a Transaction ID of “1000,” you could expect that the next Transaction ID would not be less than 1000. However, after the updates, it will be possible to receive a Transaction ID less than the one previously received.
If your system has any functionality that expects Authorize.Net-generated IDs to be sequential, please update it immediately so that you will not see any disruptions.
Additionally, please make sure that your solution does not restrict any Authorize.Net ID field to 10 characters. If you are required to define a character limit when storing any of our IDs, the limit should be no less than 20 characters.
RC4 Cipher Disablement
In an effort to ensure that all of your server-to-server communications with the Authorize.Net platform (both transactional and otherwise) maintain the highest levels of security, we will be disabling the RC4 cipher suite during the first half of 2016. A follow-up notification will be sent out once specific dates for the disablement are ready for the sandbox and production environments.
For now, if you have a solution that relies on RC4 to communicate with our servers, please update it to a current, high-security cipher as soon as possible. Please review our API best practices blog post for more information.
Sincerely,
Authorize.Net
You have opted to receive Administrative Announcements for your payment gateway account. To unsubscribe, log into the Merchant Interface and click Account from the main toolbar. Then click User Profile from the menu on the left. Select Edit Profile Information and uncheck the email types you do not want to receive. Click Submit to save any changes.
For information on how we handle customer information, please see our Spam Policy and Privacy Policy. Please do not reply to this email.
© Copyright 2016. Authorize.Net P.O. Box 8999, San Francisco, CA 94128-8999. All other marks are the property of their respective owners. All rights reserved.
|
|
Lorenzo Orlando Caum
|
April 20, 2016 at 6:39 am
Hello,
Thanks for sharing. That is a general email about changes in the future but I did not see anything about your specific account.
Was there any other questions that we could help you with?
—
Lorenzo
|
|
Theodore Salamone
|
April 20, 2016 at 1:15 pm
Lorenzo,
First of all you could email me with an address to which I could respond instead of having to resort to the forum each time. The noreply email wears thin when you ask for a response.
Second, the changes Auth.net mentions are specific to my site (and probably others0. I have restricted capabilities with tehm now because I do not have access to the workings of your system to make teh recommended changes.
And why would i post specific notes about my site to a general view forum where competitors can see what issues I am facing because I cannot make some simple changes to your payment protocol for Auth.net.
|
|
Lorenzo Orlando Caum
|
April 22, 2016 at 7:47 am
Hello Theodore,
I misread one of the URLs that Authorizenet is recommending by June 30th. It is similar to the original URL with the addition of the number 2 so I overlooked that. I’ve asked a developer to review the other items in the email as well and if changes are needed, then we’ll apply those and they will be available as a one-click update through your WP dashboard.
You can’t reply to the email notifications about your support forum post. However, you can click-through and then reply here as we provide support for Event Espresso in our support forums.
Thanks
—
Lorenzo
|
|
Theodore Salamone
|
April 28, 2016 at 9:49 am
Hi Lorenzo,
What is teh status on this Autorize.net issue?
|
|
Lorenzo Orlando Caum
|
April 28, 2016 at 10:56 am
Hi,
You can update to the latest version and there is now an option to pick the Akamai setting in the Authorizenet AIM option:
https://eventespresso.com/wiki/ee4-changelog/
Also, the old URLs will continue to work so there would be no disruption in payment processing even if you used the original settings. I clarified this with a developer as well as on the Akamai FAQs page for Authorizenet.
Thanks
—
Lorenzo
|
|
Theodore Salamone
|
April 28, 2016 at 1:59 pm
Thank you very much!
|
|
Theodore Salamone
|
April 28, 2016 at 2:06 pm
Hi Lorenzo,
I clicked the link in your response. It appears to be only for EE 4. I am still on 3. Are you saying that I need to migrate from 3 to 4 to update the Akimai Authorize.net settings?
On a related note, which I was going to ask next anyway, is EE 3 going away? Is it being developed further? Is it being maintained (and for how long) if it is not being developed further?
Are all the features and plugins for EE3 now available for EE4? I know that was not the case the last time I checked. If not all is supported in EE4, what is missing?
I am trying to finish my new perconline.org website (on a test host site now, not sandboxed.) This project has been going on for almost a year adn I am trying to finish it off. In the test site the sidebar widget display of my EE 3 listed events all have red dots behind them. Is this a security measure since I only have a one site license? Will tye automatically disappear once I replace the live site with the test site, hopefully next week?
|
|
Lorenzo Orlando Caum
|
April 28, 2016 at 5:45 pm
Hi Theodore,
The tone of the email that Authorizenet sent out makes it sound like if you do not switch, then you won’t be able to process payments. I created a ticket which was in progress before I received additional feedback from a developer and re-read the FAQs page for Akamai.
I can confirm that Authorizenet will route traffic from the original links to the new ones automatically. This means that there won’t be any disruption in payment processing.
We are continuing to maintain Event Espresso 3 including ensuring compatibility with the current version of WordPress. No new products / features are being added and we have no plans to stop supporting Event Espresso 3 in the near future.
There are several features that are not yet available in Event Espresso 3 including recurring events, waitlists, mobile apps, attendee mover. Mobile apps are under final testing and will be available in the near future. We’ve also started development on the attendee mover. Once that is out, then we’ll continue to work on other features.
On the red dots, we do not have any features that lock down Event Espresso. Technically, you can use it on any WordPress site that you would like. However, support services will be provided for the site that is enabled with your support license.
Do you have a link available to the page with the red dots?
Thanks
—
Lorenzo
|
|
Theodore Salamone
|
April 28, 2016 at 6:29 pm
Hi Lorenzo,
Thank you for all the answers. Not having to migrate right now is very important and still having items processed is a godsend.
You will not be be able to access the red dot site because it is on a development server and you need a password and user ID. If you send me a private email to redacted – Event Espresso support team – LOC I will get the info to you.
Thank you again.
Regards,
Ted
|
