Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • F Frontend
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Vincula
  • Frontend
  • Merge requests
  • !33

Merged
Created Sep 29, 2025 by Francisco Coimbra Rotilli@francisco.rDeveloper

[117] Refresh Token

  • Overview 0
  • Commits 4
  • Pipelines 4
  • Changes 4

Tarefa relacionada

https://dev.azure.com/ages-vincula/Vincula/_sprints/taskboard/Vincula%20Team/Vincula/Sprint%203?workitem=117

O que foi modificado?

Pequeno ajuste na rota api/me para utilizar a lógica de refresh token.

Ajuste no compenente NavBar para redirecionar para login quando refresh token falhar.

Correção na rota api/case/[caseId] para usar Promise (Antes causava erro de build).

Ajuste no auth service para lançar erro adequado ao falhar getCurrentUser.

Edited Oct 02, 2025 by Francisco Coimbra Rotilli
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: 117/refresh-token