Open-EO / Open-EO/openeo-python-client
Remove refresh token from RefreshTokenStore when access token renewal fails
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
In the QGIS plugin, we implement our own RefreshTokenStore. It seems that the refresh token is not removed from the RefreshTokenStore when access token renewal fails. First we check the exp claim in the refresh token, but if it doesn't exist we rely on the refresh token being removed when the access token renewal fails. It seems that's not foreseen?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the QGIS plugin's RefreshTokenStore implementation and the access-token renewal entry point. Reproduce a failed renewal, then verify that the refresh token is removed; add or update tests for this failure path if the existing test structure covers it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, authentication
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100