topic Accept JS Errors? in Integration and Testing

Accept JS Errors?

dnsBuffaloNY — Fri, 03 Aug 2018 15:11:03 GMT

I'm getting some strange errors in Sandbox this morning. I'm using Accept JS.

I'm wondering if there are any known issues with the environment.

I just started getting this error:

E_WC_14:Accept.js encryption failed.

About an hour ago, I was getting this error:

E00003:The 'AnetApi/xml/v1/schema/AnetApiSchema.xsd:transactionKey' element is invalid - The value XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX is invalid according to its datatype 'String' - The actual length is greater than the MaxLength value.

My code has not changed. It was working yesterday.

Lastly, is there a web page somewhere that posts the status of the SandBox environment?

Thanks!

Re: Accept JS Errors?

RichardH — Fri, 03 Aug 2018 16:10:14 GMT

Hello @dnsBuffaloNY

I've escalated your report to our support specialists team. We did have a minor sandbox update yesterday.

If there is a status change notice, it will be listed at https://status.authorize.net.

Richard

Re: Accept JS Errors?

ElaineM — Fri, 03 Aug 2018 16:56:19 GMT

Hi dnsBuffaloNY, I have attempted to reproduce this error using my Sandbox account and I am unable to do so. Can you provide the full request and response that you are sending/receiving from your Sandbox account? Thank you, Elaine

Re: Accept JS Errors?

dnsBuffaloNY — Fri, 03 Aug 2018 19:01:02 GMT

The "E_WC_14:Accept.js encryption failed." error I was getting before is now gone. That is, I'm no longer getting the error (I'm not sure why - but I'm not worried about it; I've moved on :) )

But I'm still having an issue, and I have a theory why I have the problem.

Here's the JSON response from the client side (HTTML/Javascript) for a recent call:

"opaqueData":
{
"dataDescriptor": "COMMON.ACCEPT.INAPP.PAYMENT",
"dataValue": "eyJjb2RlIjoiNTBfMl8wNjAwMDUzRTExQjBDNDczRDY2RDI1Q0E2MkUzMkVCREJGQThDM0RBRTM4OThEQzBBMjlDNzNGRDdEQUE5MUQ2REJDRUE5RkIxMzMzRTI3MEM3Q0U0MEY0MkU5MzA1RTcxMDRERTk1IiwidG9rZW4iOiI5NTMzMzIwNjc2NTQ4NzUxNjA0NjA0IiwidiI6IjEuMSJ9"
},
"messages":
{
"resultCode": "Ok",
"message":
[
{ "code": "I_WC_01", "text": "Successful." }
]
}

What looks strange to me is the "dataValue" seems substanially longer then I remembered. Maybe that was the "minor" enhancement that Richard mentioned(?)

I have some older Unit Tests in my code and I see the dataValue used to look like this:

dataValue = "eyJ0b2tlbiI6Ijk0OTIyOTEzMjU5NjYxMDkwMDQ2MDMiLCJ2IjoiMS4xIn0=",

(length = 60)

and now the length starting today is 278.

On the server side, I have a Asp.Net MVC application, and I'm using the .Net SDK.

The error I'm getting on the server is this:

It looks to me that .Net SDK is using XSD to validate the "transactionKey" parameter, and is throwing the error:

"The actual length is greater than the MaxLength value"

My theory is the "dataValue" string returned from Accept JS is now longer, and .Net SDK doesn't like the longer value.

I'll take a look at the .Net SDK code, but I wanted to confirm if "dataValue" length was incresed?

Thanks, Donald.

Re: Accept JS Errors?

dnsBuffaloNY — Fri, 03 Aug 2018 19:51:22 GMT

I generated a new TransactKey and ClientKey. Everything seems to be working.

Sorry for the Fire Alarm (and wasting your time reading this). I'm not sure why my old Keys were bad (they were working yesterday).

Thanks!

Re: Accept JS Errors?

Alana118 — Mon, 11 Mar 2019 09:20:13 GMT

I got grumpy and made my own sandbox and public key and it works now-

That old public client key was old or something?

So I will have to get this client to regenerate thier keys.

The public client key will not impact anything else.