You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's no other issue that already describes my problem.
Describe the Bug
When using an OIDC provider that provides a new refresh_token on a refresh grant flow, the old refresh_token is invalidated. Directus should be able to handle this by storing the new refresh_token in place of the existing refresh_token.
Preflight Checklist
Describe the Bug
When using an OIDC provider that provides a new refresh_token on a refresh grant flow, the old refresh_token is invalidated. Directus should be able to handle this by storing the new refresh_token in place of the existing refresh_token.
See discussion #10148 for further details.
To Reproduce
Use an OIDC provider that provides a new refresh_token and new access_token on a refresh grant.
See discussion #10148 for further details.
Errors Shown
Directus simply says the refresh_token is invalid. Server side logs:
What version of Directus are you using?
9.1.2
What version of Node.js are you using?
Whatever comes with the Docker container
What database are you using?
MariaDB 10.4
What browser are you using?
Chrome
What operating system are you using?
RHEL 7
How are you deploying Directus?
Docker
The text was updated successfully, but these errors were encountered: