[DEVOPS-4768] fix(auth): do not send stale tokenId on login - #49
Merged
Danny Bédard (DannyBedard) merged 2 commits intoSep 30, 2026
Merged
Conversation
Copilot started reviewing on behalf of
Danny Bédard (DannyBedard)
September 28, 2026 18:57
View session
Contributor
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Token clearing introduces a race that can cause concurrent requests to omit authentication.
Review effort: Balanced
Findings: 1
What changed in this PR
Fixes token refresh by preventing expired tokens from being sent during login.
Changes:
- Clears expired tokens before re-authentication.
- Omits empty
tokenIdheaders and adds refresh coverage. - Bumps the patch version.
| File | Description |
|---|---|
VERSION |
Bumps version to 0.21.1. |
authentication.go |
Clears the token before login. |
dvls.go |
Omits empty token headers. |
dvls_unit_test.go |
Tests expired-token refresh. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Danny Bédard (DannyBedard)
force-pushed
the
devops/DEVOPS-4768-token-refresh
branch
from
September 29, 2026 14:32
cb250e4 to
2639c4d
Compare
Copilot started reviewing on behalf of
Danny Bédard (DannyBedard)
September 29, 2026 14:46
View session
Danny Bédard (DannyBedard)
force-pushed
the
devops/DEVOPS-4768-token-refresh
branch
from
September 29, 2026 14:57
2639c4d to
f74f225
Compare
Copilot started reviewing on behalf of
Danny Bédard (DannyBedard)
September 29, 2026 15:21
View session
Richard Boisvert (rbstp)
approved these changes
Sep 30, 2026
Danny Bédard (DannyBedard)
deleted the
devops/DEVOPS-4768-token-refresh
branch
September 30, 2026 14:04
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Après l'expiration de la session DVLS (environ 7 min), le client détecte bien
is-logged = falseet se reconnecte, mais le login renvoyait le headertokenIdexpiré, et DVLS rend alors un nouveau jeton déjà mort (401). Le login part maintenant sanstokenId: le jeton est passé explicitement à la fonction internerawRequestWithContext, sans toucher au jeton partagé ni à l'API publique.Validé sur dvls-ops : connexion, attente de 8 min, requête.
masterreçoit 401, cette branche passe. Bump en 0.21.1.