an external party needs to make rest calls to Netsuite, they need it to be oauth 2.0 but don't have JWT token assertion ability, what are some solutions

AI generated answer (using internal Slack threads):

If an external party needs to make REST calls to NetSuite using OAuth 2.0 but doesn't have JWT token assertion ability, there are a few options they can consider: 1. Bearer Tokens: OAuth 2.0 can support simple bearer tokens. If the external party has the ability to generate bearer tokens, they can include the bearer token as a header in their REST calls. 2. Client Credentials or Password Grant Type: If the external service supports it, the external party can use the client_credentials or password grant type to obtain an access token. This is relatively easier to implement. 3. External Libraries: There are JavaScript libraries available that can help with OAuth 2.0. However, it's important to note that not all libraries may work with NetSuite as making outbound requests in NetSuite server scripts is non-standard. If the external party is doing something client-side, they might be able to get one of these libraries to work. Please note that the complexity of implementing OAuth 2.0 can vary depending on the external service being used. For example, if the external service is an AWS product, it may not use OAuth 2.0 and could potentially be more complex as it uses actual cryptography. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******

Do I not need JWT to generate bearer tokens? Netsuite Oauth2.0