I'm running an externally available Suitelet but would like it to interpret the saved search date filters in a different time zone. Currently it runs as the system user, which, as I'm working with a OneWorld account, not the same time zone as the end user of my Suitelet. Any tips for how I can run the Suitelet under a different user from just an external URL alone? Would it be best to convert my Suitelet to a RESTlet and use OAuth/TBA?

you probably wanted the restlet in the first place if it is an option

@battk Yes, I was planning to do that actually. I'm inexperienced with restlets though, so I have a probably stupid question: how do I add the content header to make the restlet output application/json?

the restlet's content type matches the content-type header sent in the request

Cheers.

both are fine securitywise, oauth 2.0 client credentials is likely to be supported longer than token based authentication

@battk Thanks. I'd love to learn how to implement OAuth 2.0 in NS, both for incoming connections to RESTlets and also to connect to outside services (there was an OIDC service I needed to connect to). Can these things typically be done just through SuiteScript APIs, or are other components necessary? I guess I don't understand the model well enough yet.

doing it within netsuite is usually harder than using something like node js

I see. So then you need to have nodejs hosted somewhere? How would you connect NS to the nojs instance securely? I had a colleague create a PHP script (no doubt using some OAuth library) to connect to endpoints through OIDC but I simply connected to his PHP endpoint using nlapiRequestURL. Seems like there should be a better way?

host a node js server, or use one of the many services that will let you do so

So basically you use a trusted server under your own control as an in-between to make the OAuth connections.

its the method virtually guaranteed to work

I see.