peterzog

Error authenticating to OneSpan: 404 - Not Found

0 votes

I am working through the OneSpan Sign APEX SDK and running the getSessionId() is giving me this result:

OneSpanRESTAPIHelper.OneSpanRestAPIHelperException: Error authenticating to OneSpan: 404 - Not Found - {"messageKey":"error.notFound.userNotFound","technical":"Could not find user with uid 'aXqJ5kBWyi0X'","message":"The specified user cannot be found.","code":404,"name":"Resource Not Found"}

I created the custom setting called Main and used the API key from here: https://sandbox.esignlive.com/a/admin/apiaccess

I have the OneSpan managed package installed, could there be conflicts with that?


Reply to: Error authenticating to OneSpan: 404 - Not Found

0 votes

I am still stuck.

I saw another post on this forum where the user tried another account and got past this error. So, I created a brand new sandbox account and used the new API key and I get the same error but with a different 'uid' in the error.  Is there something out of sync with my user account?

OneSpanRESTAPIHelper.OneSpanRestAPIHelperException: Error authenticating to OneSpan: 404 - Not Found - {"technical":"Could not find user with uid 'YXnaGk1R06oJ'","messageKey":"error.notFound.userNotFound","code":404,"name":"Resource Not Found","message":"The specified user cannot be found."}


Reply to: Error authenticating to OneSpan: 404 - Not Found

0 votes

I figured it out.  Silly issue.  After trying postman and seeing success I noticed that the installation instructions on github has a typo for the api endpoint.  

It says:Endpoint = https://sandbox.e-signlive.com/api (SANDBOX) || https://apps.e-signlive.com/api (PROD)

But it should say Endpoint = https://sandbox.esignlive.com/api (SANDBOX) || https://apps.esignlive.com/api (PROD)

No hyphen should be in the URL.

Source: GitHub - KadenceCollective/onespan-sign-apex-sdk: Apex SDK for OneSpan Sign

 


Reply to:

0 votes

Hi Peter,

 

Glad you figured it out! Yeah, it could be tricky that the Git Readme file said "sandbox.e-signlive.com". Actually it's not incorrect, because there does exist an instance with this URL which is so called US1 sandbox/production, versus US2 sandbox/production where the URL excludes the hyphen.

 

Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off