authorize.net problems

[delia]

I think there is an issue with a server. Authorize.net no longer shows up as an option at checkout. The secure cert appears to be fine. This did start after a.net stopped the old TLS versions. The server does have the required TLS but all versions seem to be still available. The only difference I can see between my server and this server is the setting of TLS-SRP - my server is yes and the other server is no. I really don't understand all the details around this!

Can I use the authorize.net files from 1.5.5? I don't see much difference except a new error reporting for what appears to be this very thing. I don't see that a full upgrade is worth the time or money to this particular website. I've advised them to move to a new server as this one is not going to be updated. I think that will fix the problem but would be nice to have more information about what's happening now.

[DrByte]

The only reasons the AIM module wouldn't show at checkout are:
- if the module is disabled in the Admin,
- the checkout "zone" doesn't match the customer's payment address,
- if ENABLE_SSL is set to false and/or HTTPS_SERVER and HTTP_SERVER doesn't contain an https URL, in the configure.php file.
- curl is not available to PHP
- (or in advanced cases, if you've added custom code to the update_status() function in the module, to disable it under other circumstances.)

The TLS compatibility matters would only show up when actually submitting a transaction, but that can only be done if the module actually shows during checkout.

[delia]

Bingo, in the upgrade and template switch, somehow the enable ssl switch was false where the site is configured for all ssl - both HTTPS_SERVER and HTTP_SERVER has https.

Thanks so much!