cancel
Showing results for 
Search instead for 
Did you mean: 

secure vs. secure2 after recent updates.

I'm currently connecting just fine to https://secure.authorize.net/gateway/transact.dll

after updating security certificates (which was so much fun using cfmx7 and java 1.4).

 

I cannot connect to secure2.authorize.net.

 

I'm assuming I'm missing some intermediary certificate for secure2, but have them correctly installed for secure.authorize.net.

 

 

Is this even an issue if I can successfully connect and use https://secure.authorize.net/gateway/transact.dll ?

 

I was under the impression that the updates for the secure.authorize.net were pushed out quite a while back.

 

Many Thanks for any clarifications.

 

 

 

 

iceninexp
Member
1 ACCEPTED SOLUTION

Accepted Solutions

http://www.authorize.net/support/akamaifaqs/

secure and secure2 is different

 

not till next year

Phase Two (June 2016) – We will automatically direct all of our existing transaction processing URLs to connect through Akamai in June of 2016. After this change, all transaction URLs will connect to Authorize.Net through Akamai.

View solution in original post

RaynorC1emen7
Expert
2 REPLIES 2

http://www.authorize.net/support/akamaifaqs/

secure and secure2 is different

 

not till next year

Phase Two (June 2016) – We will automatically direct all of our existing transaction processing URLs to connect through Akamai in June of 2016. After this change, all transaction URLs will connect to Authorize.Net through Akamai.

RaynorC1emen7
Expert

Okay, so I apparently need to install some more security certificates and check connectivity.

 

Many Thanks!