Dtscci 3814 redis integration new branch#3736
Open
elvianihuseyin2 wants to merge 37 commits intoDTSCCI-3202-TESTfrom
Open
Dtscci 3814 redis integration new branch#3736elvianihuseyin2 wants to merge 37 commits intoDTSCCI-3202-TESTfrom
elvianihuseyin2 wants to merge 37 commits intoDTSCCI-3202-TESTfrom
Conversation
added 8 commits
January 29, 2026 13:18
…814-redis-integration-new-branch # Conflicts: # yarn-audit-known-issues
Contributor
Plan Result (aat) |
mounikahmcts
approved these changes
Feb 10, 2026
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.
JIRA link
https://tools.hmcts.net/jira/browse/DTSCCI-3814
Change description
ISSUE BEFORE:

IDAM token is stored inside the COOKIES under name 'SESSION_ID"
FIXES:
Integrating REDIS to the cmc-frontend
Only store the Redis token inside the cookies under cmc-cookie-session
IDAM token are now cached inside REDIS
Does this PR introduce a breaking change? (check one with "x")