04-02-2020 01:48 PM
I’m working with an application that supports ‘Client Credentials’ and ‘Authorization Code’ grant types in the authorization request; however, doesn’t support refresh tokens. What is the value of selecting the ‘Client Credentials’ grant type in the REST OAuth2 Account? Does the REST OAuth2 Account make the authorization request and get the token when the first document enters the REST snap that’s using the account? What’s the purpose of the ‘Authorize’ button when the grant type is ‘Client Credentials’ since the token will expire at some point? Is it just to validate that the account has been configured correctly?
I have the same questions if the grant type is ‘Authorization Code’ and the api doesn’t support refresh tokens.
01-21-2021 11:17 AM
Looks like that fix was in 4.21.
03-25-2023 06:51 PM
Hi,
Hope you are doing well! Would you mind helping to check why same oauth2 is working for one node but not for other node after march 11 release
It was working fine for both the node before this, all of sudden it stoped working and we are getting 500 error messages on authorize button click.
02-09-2021 04:47 AM
Sorry for a delayed response. My bearer token is refreshed even though I don’t get a refresh token while creating the account. Thanks for all your help.