SSL related error with Authorize.net AIM (self-signed certificate)

[jerrygarciuh]

Hello,

We have a v1.5.3 store in development on a sub-domain of live site. Live site has existing SSL cert. Since we only need the sub-domain for a week or two we added a self-signed cert to server. Accessing through FireFox we added exception and are able to access site at https://dev.mysite.com/mystore

mystore/myadmin/includes/configure has been updated to

define('HTTP_SERVER', 'http://dev.mystore.com');
define('HTTPS_SERVER', 'https://dev.mystore.com');
define('HTTP_CATALOG_SERVER', 'http://dev.mystore.com');
define('HTTPS_CATALOG_SERVER', 'https://dev.mystore.com');
define('DIR_WS_HTTPS_CATALOG', '/mystore/');
// secure webserver for admin?  Valid choices are 'true' or 'false' (including quotes).
define('ENABLE_SSL_ADMIN', 'true');
// secure webserver for storefront?  Valid choices are 'true' or 'false' (including quotes).
define('ENABLE_SSL_CATALOG', 'true');

After enabling cookies and cache cleared and we were prompted to set new pass based on SSL change.

However when we try to configure Authorize.net AIM or PayPal eg at
https://dev.mysite.com/mystore/myadm...thorizenet_aim

We get

ALERT: For security reasons, Installation of this module is disabled until your Admin is configured for SSL.

So we tried in browsers and on computers which had never accessed the site before. Same results.

I doubt it is relevant but FYI whole dev site uses htaccess basic auth to prevent access but since we are authenticated I don't see how that could have anything to do with this.

So- questions are

1. Is problem the result of self-signed certificate?
2. Can we resolve (eg configure and test Authorize.net AIM) without paying for trusted root issued certificate?

[jerrygarciuh]

So this was resolved by forcing SSL outside admin...

define('HTTP_SERVER', 'https://dev.mystore.com');

[DrByte]

Exactly.

That's why immediately above the defines for HTTP_SERVER, HTTPS_SERVER, etc, you see the following comments:

/**
 * WE RECOMMEND THAT YOU USE SSL PROTECTION FOR YOUR ENTIRE ADMIN:
 * To do that, make sure you use a "https:" URL for BOTH the HTTP_SERVER and HTTPS_SERVER entries:
 */