-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refresh_Token Expires within a few hours #234
Comments
I haven’t seen any similar issue. I suggest you create some kind of audit log with the tokens. |
Same issue here. Created the token in the afternoon and the morning after it was invalid. I guess this is not related to the C# client library but still a vital issue to solve if we are to be able to work with our integration. |
Did you generated the tokens with the Fortnox SDK? Just so you know, this repository is not affiliated with Fortnox anymore. If you feel the issue is not caused by this library, please write directly to Fortnox official support and describe the problem to them. |
The token was created with the SDK but I spoke with the support instead since I noticed this repo wasn't maintained by Fortnox. They however do not acknowledge that this error exist so I'll keep an eye out for it happening again before we go live. |
I have been facing this same issue for the last 2 weeks. our application is in production and now this issue has started appearing and is very frustrating for our customers as they need to reactivate the token. I believe there is some sort of throttling on this endpoint. |
I have apps that is running the SDK with multiple customers. And have done so for several months with no problem. |
@xpagedeveloper I am making blocking calls to refresh the tokens but the token gets invalidated on higher request rates. I sent 30 requests simultaneously and the error was reproducible. |
I can imagine how frustrating this issue was for me and can be for anyone 😀 Here are a couple of suggestions that you can follow: 1). Make sure there is only one user at a time generating/using the App and the generated auth creds. if 2 users(consider A dev and a QA) using the same then it is gonna produce the same issue. |
Hi @xpagedeveloper xpagedevelope 1). How often do you generate access and refresh tokens? |
1). How often do you generate access and refresh tokens? 2). What is the expected/average number of Apis calls per customer (for which you generate the tokens) on an average day you make? aprox 1-30 /customer and day |
If you login with the same Fortnox API user again, you invalidate the previous refresh token. |
Yes if you request a new access token using a refresh token any previous refresh tokens is invalid. |
Hi
I see some issues with refresh_token.
After getting authCode, I got access_token(valid for 1 hr) and refresh_token(valid for 31 days, I saved in DB)
After 1 hr access_token is expired and I generated a new access_token using the refresh_token(from my DB).
Now I got new access_token and refresh_token (I updated the new refresh_token in my DB)
After a few hours(>7-8 hours) API says "Request failed: Invalid refresh token"
That is not the expected behavior.
Has anyone faced a similar issue before? :)
The text was updated successfully, but these errors were encountered: