nextcloud / nextcloud/Android-SingleSignOn
Option to create new token on `TokenMismatchException`
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 74
- Forks
- 36
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 17
Description
Using Nextcloud, as well as Deck and Notes for Android, I have an issue where neither of the apps are able to authenticate anymore.
This is my fault, as I have revoked their tokens in the Web UI after a backup restore.
The app helpfully offer to restart them, or to wipe them and obtain a new token. I would generally do the latter, but in this instance I have changes in the app that haven't been synced to the server, so I don't want to wipe their data.
It would be useful to offer the opportunity to reauthenticate and generate a new token when this happens, rather than having to restart/wipe.
Contributor guide
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 tracing where TokenMismatchException is handled in the Android library and how the restart or wipe choices are presented. Review the authentication flow used by Deck and Notes for Android, then define the reauthentication path. Done means a revoked-token user can obtain a new token without wiping unsynced app data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- authentication, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100