Integrate Akamai

[tsomik1]

I am trying to integrate Akamai SureRoute in our system. 

1.I have read that url is changing from https://api.authorize.net/xml/v1/request.api to https://api2.authorize.net/xml/v1/request.api. On another blog I found that I can still use the same url

2. I am using coldfuson 10. On this link http://www.coldfusionmuse.com/index.cfm/2014/12/8/colfusion-jvm-versions-sslv3-tls

I found out that I need to run Java 1.8 I do have 1.7 . Do i need to update to 1.8?

And what else would I Need to make a smooth transition

[dev-usa]

In your email you state, "If you'd rather wait until June 30, don't change the URL and we'll take care of the rest."  I am using AIM in one of my sites.  Does this mean that I can ignore the announcement?  And, where do I find information about what "Akamai SureRoute" is?!?

[RichardH]

@dev-usa

We've created a technical FAQ for developers regarding Akamai SureRoute:  https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Akamai-SureRoute-Techn...

Richard

[dev-usa]

The following is in my WP plugin:

https://api.authorize.net/xml/v1/request.api

This URL needs changed and the way that I read it I can do that immediately instead of waiting until June 30.  Correct?

[tsomik1]

Basically, my understanding was I can keep everything as is and on June 30 Authorize.net will already make an adjustments to the existing url 

[RichardH]

@dev-usa @tsomik1

You are both correct.  Your options include changing to the new endpoint, or do nothing and the existing endpoints will be sent through Akama SureRoute automatically.

Richard

[alambert-wf]

I was reading this thread because it mentioned the AIM endpoints

Old - https://secure.authorize.net/gateway/transact.dll

New - https://secure2.authorize.net/gateway/transact.dll

I have a ColdFusion 10 application using the AIM method and Post Form Fields using CFHTTP.

It works today using "secure.authorize.net". Will it continue to work after June 30th?

The reason I ask is because we did change it to "secure2.authorize.net" a few months ago and it worked until the middle of this month (June). We had to revert back to the old endpoint.

[RaynorC1emen7]

they update the faq on it

read

https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Akamai-SureRoute-Techn...

[Lilith]

@alambert-wf We've changed our Akamai strategy, and have moved to opt-in, without a deadline. This means that we won't be switching secure.authorize.net to Akamai SureRoute.

That said, secure2.authorize.net should certainly work fine. Did you report the issue you encountered? Is there a chance you saw an HTTP 403 error?