Why
We have two code paths for loading the session state in sso-proxy that we kept in until the cookie refresh period expired for sso in production. Both code paths were kept in place so that having an invalidly decrypted session cookie would not affect the UX for those logging into sso-proxy with the sessions encrypted the old way. We can now remove that code path.
This will involve removing:
Why
We have two code paths for loading the session state in
sso-proxythat we kept in until the cookie refresh period expired for sso in production. Both code paths were kept in place so that having an invalidly decrypted session cookie would not affect the UX for those logging into sso-proxy with the sessions encrypted the old way. We can now remove that code path.This will involve removing:
OldCookieCipherandOldCookieSecretfrom theOAuthProxystruct.NewOAuthProxyErrRefreshCookieLoadCookiedSession