We have an integration that communicates with NetS...
# integrationss
Steve Schmechel
06/03/2020, 7:03 PMWe have an integration that communicates with NetSuite and synchronizes certain data between two systems 24/7.
It currently uses token-based authentication (OAuth 1.0).
Is there any advantage to switching to OAuth 2.0?
We have not heard that the existing TBA is being deprecated any time soon.
We are able to calculate oath_signature on each request, so we don't have a resource issue like a mobile device might have.
On the other hand, we have a library available to handle the OAuth 2.0 token negotiation, so implementing this would not be difficult.
Any ideas on pros vs. cons of making the switch?
b
battk
06/03/2020, 11:00 PMCurrently oauth 2 is unusable for an integration
battk
06/03/2020, 11:01 PMThe refresh token expires in 7 days
battk
06/03/2020, 11:01 PMThat means a user must grant access every 7 days
s
Steve Schmechel
06/04/2020, 3:54 AMIs that a bug? That doesn't follow from the NS documentation or our experience with other API's using OAuth 2.0.
b
battk
06/04/2020, 3:56 AMbattk
06/04/2020, 3:57 AMthe blue note
battk
06/04/2020, 3:59 AMstandard oauth 2 is Short-lived access tokens and long-lived refresh tokens
battk
06/04/2020, 4:00 AMnetsuite has chosen both short lived access tokens and short lived refresh tokens
s
Steve Schmechel
06/04/2020, 4:25 AMInteresting. Seems like it is targeted for simple integration of user-driven tools. Thanks for your feedback.
2 Views