[TECH] Ne pas stocker de timestamp pour la révocation de session (PIX-24133) - #17394
Merged
Conversation
|
Choisir les applications à déployer :
Important N'oubliez pas de déployer l'API pour pouvoir accéder aux fronts et/ou à l’API MaDDo. |
lego-technix
reviewed
Sep 4, 2026
lego-technix
reviewed
Sep 4, 2026
lego-technix
reviewed
Sep 4, 2026
nlepage
force-pushed
the
pix-24133-revoke-session-storage
branch
from
September 4, 2026 13:03
c487f84 to
cd164d0
Compare
nlepage
force-pushed
the
pix-24133-revoke-session-storage
branch
from
September 4, 2026 13:12
cd164d0 to
5f0b6fe
Compare
nlepage
force-pushed
the
pix-24133-revoke-session-storage
branch
from
September 7, 2026 07:58
7746025 to
a257136
Compare
nlepage
marked this pull request as draft
September 7, 2026 08:17
nlepage
force-pushed
the
pix-24133-revoke-session-storage
branch
from
September 7, 2026 09:18
a257136 to
92b16f3
Compare
nlepage
marked this pull request as ready for review
September 7, 2026 09:18
nlepage
force-pushed
the
pix-24133-revoke-session-storage
branch
from
September 7, 2026 09:37
92b16f3 to
8e83de9
Compare
lego-technix
reviewed
Sep 7, 2026
lego-technix
approved these changes
Sep 7, 2026
lego-technix
left a comment
Contributor
There was a problem hiding this comment.
✅ Lu et testé fonctionnellement avec succès avec Firefox 🦊 et Linux 🐧
nlepage
force-pushed
the
pix-24133-revoke-session-storage
branch
4 times, most recently
from
September 9, 2026 13:33
9892e7d to
f460543
Compare
Expiration was implemented incoherently in various methods. InMemoryKeyValueStorage is now used only in unit tests which makes implementing expiration non necessary.
RevokedUserAccess model
RevokedUserAccess model Co-Authored-By: "LEGO Technix" <109212476+lego-technix@users.noreply.github.com>
Co-Authored-By: "LEGO Technix" <109212476+lego-technix@users.noreply.github.com>
Co-Authored-By: "Guillaume Lagorce" <guillaume.lagorce@pix.fr>
nlepage
force-pushed
the
pix-24133-revoke-session-storage
branch
from
September 9, 2026 14:21
f460543 to
ce758d6
Compare
Libouk
approved these changes
Sep 9, 2026
pix-service
pushed a commit
that referenced
this pull request
Sep 10, 2026
# [5.499.0](v5.498.1...v5.499.0) (2026-09-10) ### 🚀 Amélioration - [#17418](#17418) Ajouter l'ID de la catégorie à la modification d'organisations en masse (PIX-23565) - [#17452](#17452) Ajouter un sélecteur de catégorie sur la fiche d'édition d'une organisation (PIX-23563) - [#17429](#17429) migration pour remettre des contraintes "not nullable" supprimés par inadvertance (PIX-24132) - [#17404](#17404) Récupérer les CGU de l'utilisateur de Pix Certif en passant par le nouveau modèle (PIX-22441) ### 🐛 Correction - [#17460](#17460) Ne pas jeter d'erreur 500 lors de la concurrence de création d'invitation à un CDC (PIX-24219) ### 🏗️ Tech - [#17410](#17410) Créer un script permettant l'ajout des ids de contenus formatifs pour la mise en avant en fin de parcours (PIX-24009). - [#17070](#17070) Déplacer le pré-handler d'Assessment dans shared - [#17394](#17394) Ne pas stocker de timestamp pour la révocation de session (PIX-24133) ### ⬆️ Montée de version - [#17419](#17419) Update dependency @1024pix/pix-ui to ^68.1.1 (mon-pix) - [#17462](#17462) Update dependency @1024pix/pix-ui to ^68.1.3 (junior) - [#17428](#17428) Update dependency @testing-library/user-event to ^14.6.6 (mon-pix) - [#17449](#17449) Update dependency @testing-library/user-event to ^14.6.7 (mon-pix) - [#17445](#17445) Update dependency @xmldom/xmldom to >=0.9.12 (admin) [SECURITY] - [#17446](#17446) Update dependency @xmldom/xmldom to >=0.9.12 (certif) [SECURITY] - [#17369](#17369) Update dependency js-yaml to v5.2.2 [SECURITY] - [#17442](#17442) Update dependency nodemailer to v9.1.1 [SECURITY] - [#17447](#17447) Update dependency protobufjs to >=8.6.6 (api) [SECURITY] - [#17440](#17440) Update dependency vitest to v4.1.11 [SECURITY]
Contributor
|
🎉 This PR is included in version 5.499.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
☀️ Problème
Une session est révoquée définitivement, donc il n’est pas nécessaire de stocker un timestamp de fin de révocation.
⛱️ Proposition
Cesser de stocker le timstamp de révocation de session, on stocke une chaîne vide à la place, la présence de la clé est suffisante.
🧴 Remarques
N/A
🏊 Pour tester
Vérifier qu’il n’y a pas de régression au niveau de la révocation de session avec le feature toggle actif.
Le feature toggle est actif sur la RA.