Testing a new RESTlet with POSTMAN we have created...
# suitescript
n
Testing a new RESTlet with POSTMAN we have created a new Integration and issued a New Access Token for the User with the Role having permission Setup/Log in using Access Tokens = Full. Stubbornly we are receiving back 401 "_error error code: INVALID_LOGIN_ATTEMPT error message: Invalid login attempt._" The Login Audit in the target account shows that it is recognising the User and the Application and the error is "*InvalidSignature*". SA 81695 looked promising but doesn't appear to be the problem here. Using the same Postman request I switched everything to a request on a different account just replacing the keys and account number. That account returns that the script is invalid which it probably is for that account bu tin order to tell me that the Authentication must have worked. This makes me think my Postman settings are OK. Any tips on where you would look next?
b
you can try sharing the authorization parameters (including the advanced section) from postman
or you can try taking a look at NetSuite's Working with REST Web Services Using Postman example collection works.
n
message has been deleted
Realm is same as Account ID
b
advanced tab too
s
@Netsuite Tragic the realm will need to be in caps - and also if it's in sandbox, it's an underscore not a hyphen
b
assuming you arent doing something wrong with capitalization of the realm id, that looks correct
s
and i've also seen the realm ids of some US provisioned account to be different in company preferences and URL to the actual one, the only one that can be trusted is the one in suiteanswers contact support
n
I've tried caps/small caps. I used the Account ID from "SOAP Web Services Preferences". I think it's an account issue, something I've done in the Set of Roles, App, User.
Sciuridae54696d it is a TSTDRV btw
b
unless you setup the deployment audience wrong, the only permission needed is
Log in using Access Tokens
might not actually be able to do anything useful, but your login attempt can succeed
s
TSTDRV shouldn't be an issue "TSTDRVXXXXXXX" works fine as a realm, ^ yup that role setting is required for the role on your access token
n
Deployment is set to All Roles but my thinking is that the login fails before that.
s
i'm assuming you did actually enable token-based authentication from the enable features right? 😆
n
@Sciuridae54696d that's a fair question but yes to that one.