maproulette / maproulette/maproulette-backend
Store OAuth token so we don't need to get a new one every time a user signs in
Open
Nobody has claimed this yet.
BACKLOG
- Dominant language
- Scala
- Stars
- 53
- Forks
- 39
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
When we receive an access token from OSM when a user signs in, we should store it (securely) so we can retrieve and re-use it and don't need to generate new access tokens every time a user needs to sign in again.
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
No files or tests are named. Start by locating the OSM sign-in/OAuth flow and identify where access tokens are received and authentication state is persisted. Define secure storage, reuse, expiration, and revocation behavior, then add coverage showing a later sign-in can reuse a valid token.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100