Oauth Data Refresh called multiple times on token expire scenario #288
Unanswered
balagurusurendar
asked this question in
Q&A
Replies: 2 comments 2 replies
-
|
Could you provide examples of where you are calling your refresh token method? If you use the inbuilt authentication logic, then you shouldn't need to call refresh token at all; the framework will do it for you. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Ah ok, that is bizarre. Could you please share your full authentication code flow - redacted and obfuscated as needed - so we can see how it's structured please? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
I created a custom connector for my scenario that will fetch rest api to fetch data from cloud. Connector authenticated using Oauth connection.
for Initial token fetch it's working fine it is fetching single time. when token expires on some time, refresh token calling multiple times.
light debug & found refresh tables running in parallel threads made this scenario.
myself refreshing 20 to 30 tables at a same time. so when token expires in between them leads to this.
what to do for make OAuth Refresh function synchronized?
my refresh function will return the json look like below
{"access_token":"1000.17631e4193b64f6f242ee3ff9411ea0b.fd5c7ab3db39169375c6fea375f77f80","scope":"****","token_type":"Bearer","expires_in":3600}
Is anything problem with this json? or connector expecting this json needs to be in different format?
Note: Individual thread refreshing the token works & each thread gets a different token from server, further api calls also successful. my issue is that calling refresh multiple times for token leads to blocking myself from fetching token for some time.
Beta Was this translation helpful? Give feedback.
All reactions