-
Notifications
You must be signed in to change notification settings - Fork 8
ATO-1565: remove orch setters #6265
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
base: main
Are you sure you want to change the base?
Conversation
aa78550
to
9c568de
Compare
76e4f86
to
da35f74
Compare
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.
Deployed to dev and ran through an uplift journey - no issues
Removes the null-ing out of this value when the shared session is copied for max age handling.
This test was added as part of this commit: 037f9b2 which added behaviour for a mismatch in bsid cookie and the session value. The previous name was also inaccurate due to the fact that the request included bsid cookie. I think this test was supposed to test the mismatch, and with subequent changes has become a bit more inaccurate. This updates the tests to be a bit more specific to the mismatch case.
da35f74
to
103cd19
Compare
|
LGTM! |
Approved - but understanding look into some discrepancies between the shared and orch session for CCS. |
Wider context of change:
We previously migrated this field to the separate session stores for both Auth and Orch. However we continued to set the value in orchestration and left in logging which checked if the values were in sync. We've stopped reading the value in auth and we only get this in Orch in a few places:
Once we remove these we can stop setting in Authentication.
What’s changed:
Manual testing:
Checklist
Related PRs