Enom Sandbox

[BlestaUser00]

When I use non-sandbox mode with the eNom module, it works fine.  However, when I use sandbox mode I get an error "The user and key combination appear to be invalid, or your Enom account may not be configured to allow API access"

 

Enom is not sure why.  They are asking for the full API command and response for this error.

 

Where can I located this?

[Tyson]

Look under [Tools] -> [Module Logs], and click on the table row for eNom to see the API logs.

 

Using the sandbox requires different sandbox credentials than your live account. If you are using your live account credentials for both live and sandbox, then that would be why you received the error.

[BlestaUser00]

I only see cPanel logs under module logs.

[edunjoroge]

Am also experiencing this was it solved and how do you solve it?

[Blesta Addons]

Am also experiencing this was it solved and how do you solve it?

the answer is

Using the sandbox requires different sandbox credentials than your live account. If you are using your live account credentials for both live and sandbox, then that would be why you received the error.

 

[Tyson]

FYI, you might encounter this issue with the sandbox when using correct sandbox credentials in the case that your server and Enom's sandbox API server are unable to negotiate an SSL encryption algorithm to use for communication. I'm guessing the live and sandbox enom servers support different algorithms which accounts for the difference between being able to connect to the live server and not the sandbox.

[edunjoroge]

Your right Tyson, that was the issue.

 

In our case we disable connection over SSL(its unsafe but its only during development) as you suggested on PM and it worked.

 

Thank You

[dieselb0y]

Hey guys.. I have the same problem .. but I don't find a way to get the sandbox working ... My password for the enom reseller test is different from the live one ... but it's not working ..

 

It's telling me The user and key combination appear to be invalid, or your Enom account may not be configured to allow API access.

[Tyson]

It sounds like you may have the same issue as edunjoroge, where no connection could be established over the API because the servers were not able to negotiate which encryption algorithm to use. You could either add support for additional algorithms on your server, which the eNom server also supports (whatever they may be), or you could disable SSL with the sandbox entirely. The latter is the simplest work-around that edunjoroge used, but it means that all sandbox actions will be performed over HTTP, insecurely. It would be possible for listeners to view your sandbox credentials in plain-text.

 

If you wanted to try disabling SSL altogether for the sandbox, update /components/modules/enom/apis/enom_api.php to change the sandbox URL protocol from https to http.

i.e. change:

const SANDBOX_URL = "https://resellertest.enom.com/interface.asp";

to:

const SANDBOX_URL = "http://resellertest.enom.com/interface.asp";