maproulette / maproulette/maproulette-backend
Session lost after second login attempt (Kubernetes deployment)
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 53
- Forks
- 39
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
I deployed MapRoulette in my Kubernetes cluster with the frontend served at https://maproulette.stg.test.cloud.
On the first login using OpenStreetMap credentials, the authentication flow succeeds and I am able to access the dashboard.
However, when I sign out and try to log in again, the backend (/auth/callback) still succeeds, but immediately after that the frontend calls /api/v2/user/whoami, which returns a 401 Unauthorized. This forces the frontend to sign me out again.
Steps to reproduce:
- Deploy MapRoulette frontend and backend in Kubernetes.
- Log in via OSM for the first time — works fine.
- Sign out.
- Log in again with the same OSM account.
- Observe that the backend login succeeds, but the whoami call fails and the frontend signs out automatically.
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 the authentication flow around /auth/callback and the subsequent /api/v2/user/whoami request, then reproduce the second-login sequence in the Kubernetes deployment described. Done means signing out and logging in again with the same OpenStreetMap account leaves the frontend authenticated and makes whoami return successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, scala
- Domain
- api, authentication, backend, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100