Description of problem: Once logged in, after a period of time after the timeout we get a 404 or 403 error when trying to login to the Hub console. The only way to get around the issue is to delete the cookies within our browser and login again. Version-Release number of selected component (if applicable): ACM 2.2 How reproducible: Occurs repeatedly across all clusters. Steps to Reproduce: 1. Login with valid credentials 2. After the timeout period and the session expires, attempting to log back in returns a 403 or 404 error. Actual results: Console returns errors on the attempted login. Expected results: Login succeeds. Additional info:
G2Bsync 920923121 comment clyang82 Thu, 16 Sep 2021 13:53:22 UTC G2Bsync Agree to fix it in 2.4. Thank you.
New git link: open-cluster-management/backlog/issues/16412
G2Bsync 963978452 comment clyang82 Tue, 09 Nov 2021 09:41:52 UTC G2Bsync fixed in upstream - https://github.com/openshift/oauth-proxy/pull/234
G2Bsync 975505072 comment clyang82 Mon, 22 Nov 2021 13:08:24 UTC G2Bsync Need to log a bugzilla ticket to trace it in oauth-proxy since there are no any feedbacks from upstream.
G2Bsync 978912445 comment clyang82 Thu, 25 Nov 2021 07:38:01 UTC G2Bsync Log a bugzilla on OpenShift team - https://bugzilla.redhat.com/show_bug.cgi?id=2026573
env info is here - https://docs.google.com/spreadsheets/d/1yg75xNpeO1i_K39D43FZmMauQe2d2OuJ1UjunX7jz3A/edit?pli=1&skip_itp2_check=true#gid=0&range=B23
the PR was merged yesterday - https://github.com/stolostron/management-ingress-chart/pull/130. please find a latest build to verify.
This issue is fixed by 2.5.0-DOWNSTREAM-2022-04-20-06-50-05， close it.