RE: Issues Generating a REST Web Services Signature

Anyone have any insight into creating the signature for a REST API SuiteQL signature?  I have one for authenticating and calling a RESTlet script, and it works just fine in my app, but when I try to call the REST API for a SuiteQL query, I keep getting signature errors.

Guessing I must be missing something obvious.  Changing the URLs to the SuiteQL ones keeps returning me error: “error=”token_rejected”, error_description=”Invalid login attempt.””…  But my TBA credentials work perfectly fine with a RESTlet URL instead…

I’m generating my signature using Crypto JS.

CharlesBastian Rookie Asked on December 9, 2020 in SuiteTalk.
Add Comment
2 Answers

My personal recommendation would be to use OAuth 1.0a. Otherwise expect to share your code and hope someone can see the issue.

Intermediate Answered on December 10, 2020.

Do you have any documentation on generating the signature for the REST Web Service API?  I am using OAuth 1.0.  But, I can’t use Node.

on December 10, 2020.

Not sure what environment you are using, but OAuth 1.0a is universal enough to run in both browsers and node.

on December 10, 2020.

Yeah, I’m not running in a browser or Node.  The issue is not running OAuth, though.  I’m trying to figure out why the signature works fine when calling a RESTlet URL, but does not work when I try to call the REST web services suiteQL URL.

I can’t find anything in the docs about generating the signature for REST Web services, though… :/

on December 10, 2020.

Same signature generation for both. I’ve used bascially the same code for both RESTlet and the Suitetalk REST using OAuth 1.0a in node. You probably need to share your code for more help

on December 10, 2020.

Yeah, I’m using the same signature code.   The only difference I see is the URL.  I’ve tried adding the query string (same as for RESTlets) and not adding it, tot he signature generation.  Both ways I get the same Invalid Signature error.

 

on December 10, 2020.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.