Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • pubsweet pubsweet
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pubsweetpubsweet
  • pubsweetpubsweet
  • Issues
  • #425

[tokens] Subcription reads wrong token

Steps to reproduce:

  1. Log in as a user
  2. Let the token expire (might make sense to hard-set it to 5 seconds on the server)
  3. Log out and log back in
  4. The server starts throwing "Bad token" errors, as it is reading the token from the first login.

This essentially makes the app broken, unless the user reloads (which we cannot count on).

Steps reproducible in the latest develop branch of micropubs, but seems to be unrelated.

Assignee
Assign to
Time tracking