-
Notifications
You must be signed in to change notification settings - Fork 0
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
Token refresh issues #92
Comments
Hi Aleksandr. |
Also.. the redirect_uri looks to be url-encoded.. not sure it should be |
Hello @AndersSoee! We are totally aware of the refresh token rotation and it works nicely when it works. Also the redirect_uri being encoded is totally irrelevant thing, it's how the request body is to be encoded when 'application/x-www-form-urlencoded' content-type is used. We were able to figure out that you are loosing refresh tokens when request timeout is reached. Please refer to the following example. As you can see from the following logs we were able to refresh tokens nicely for a while (although data fetching for the account in the example never worked), however after the timeout refresh token got lost. As you can see we are using 60 second timeouts, which are already very long and we can not increase it. If necessary we can provide large number of examples when token refresh is not completed within 60 seconds.
I'd suggest to devote this issue to the token refresh issues and we'll use #81 for discussion of the transaction fetching issues. |
Between 2024-11-27 01:00:00 and 2024-11-27 01:32:00 (UTC), a scheduled database maintenance job caused degraded performance for the authentication service. |
@AndersSoee many thanks for the feedback. Would it help you to spot the issue if we share all cases when token refresh request timed out? |
@AndersSoee @mathies1988 would it make sense if we use 10 seconds timeout when making token refresh? My assumption is based on this comment: #81 (comment) |
Yes, a 10 sec timeout would make perfect sense. |
Dear Team,
Your urgent assistance required. I cannot figure out why after we get
'Server error'
consequent transaction requests are returned with'"error":"invalid_grant","error_description":"The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client."'
error.It happens only for 2 of our partners.
Here is an example of one partner's client requests:
Successful:
Server error response:
Invalid status value response:
Not sure what needs to be changed for successful requests. Maybe frequency or certain missing parameters on our end or on clients end? Any kind of insight is much appreciated.
Our contact email: [email protected]
Kind Regards,
Aleksandr Kovger
Support Specialist at Enable Banking
The text was updated successfully, but these errors were encountered: