fix: bug token when change bal #950
Merged
Conversation
This file contains 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.
CONTEXT
Lorsque l'on est sur /bal/... qui est
en cours de mise a jouret que l'on revient sur l'accueilEt qu'on reclique sur la bal en question
Celle ci est maintenant
en attente d'habilitationEXPLICATION
Lorsque l'on retourne sur l'accueil, nous forcons le OpenApi.TOKEN (pour savoir si les bal sont habilité), le token est alors désynchro entre celui de OpenApi.TOKEN et du TokenContext.
Comme le Token du TokenContext n'a pas changé, le reloadHabilitation ce lance avec un OpenApi.TOKEN erroné, ce qui nous donne un une 403.
RESOLUTION
On set le token de OpenApi.TOKEN et du TokenContext a null quand il n'y a pas de balId (dans la requète)