-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BAU: session management fix #121
base: main
Are you sure you want to change the base?
Conversation
let id: string; | ||
if (request.auth && request.auth.credentials && request.auth.credentials.accountId) { | ||
id = `${request.auth.credentials.accountId}:${request.params.id}`; | ||
request.logger.info(`[ACTIVATE-SESSION] get user account id for the session key ${id}`); | ||
} else { | ||
id = `${request.yar.id}:${request.params.id}`; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this feels like an unrelated change?
edit: ah I thought this PR was just for hot reload fix. This should be two PRs - let's keep separate changes as separate PRs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also - I'm not convinced we do actually need this after some more investigation, see thread in forms tech 👀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
broke down to 2 pr's #122
remove changes into different PR
011e579
to
1439361
Compare
Quality Gate passedIssues Measures |
Change description
In this change it consists of following fixes for the form runner
<request.yar.id>:<form-name>:<application_id>
but in this method there is an issue if there is a user which is trying to go through the form in a deployment time then
request.yar.id
changing and then next request it cannot see the cache so in this new implementation we have introdused account id for the cache key<request.auth.credentials.accountId>:<form-name>:<application_id>
So, this change will guarantee that. user will retrieve the session from cache