Bug 1981945

Summary:	ACM Console 403/404 Errors on Login after Time Out
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	James Young <jayoung>
Component:	Core Services / Observability	Assignee:	Chunlin Yang <chuyang>
Status:	CLOSED CURRENTRELEASE	QA Contact:	cqu
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhacm-2.5	CC:	chuyang, ecai, juhsu, smeduri
Target Milestone:	---
Target Release:	rhacm-2.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-10-03 20:18:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description James Young 2021-07-13 18:53:42 UTC

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:

Comment 7 Mike Ng 2021-09-20 13:25:27 UTC

G2Bsync 920923121 comment 
 clyang82 Thu, 16 Sep 2021 13:53:22 UTC 
 G2Bsync Agree to fix it in 2.4. Thank you.

Comment 8 juhsu 2021-09-22 18:27:57 UTC

New git link:  open-cluster-management/backlog/issues/16412

Comment 9 bot-tracker-sync 2021-12-07 22:27:12 UTC

G2Bsync 963978452 comment 
 clyang82 Tue, 09 Nov 2021 09:41:52 UTC 
 G2Bsync fixed in upstream - https://github.com/openshift/oauth-proxy/pull/234

Comment 10 bot-tracker-sync 2021-12-07 22:27:13 UTC

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.

Comment 11 bot-tracker-sync 2021-12-07 22:27:15 UTC

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

Comment 19 cqu 2022-04-21 02:08:28 UTC

env info is here - https://docs.google.com/spreadsheets/d/1yg75xNpeO1i_K39D43FZmMauQe2d2OuJ1UjunX7jz3A/edit?pli=1&skip_itp2_check=true#gid=0&range=B23

Comment 20 Chunlin Yang 2022-04-21 05:38:07 UTC

the PR was merged yesterday - https://github.com/stolostron/management-ingress-chart/pull/130. please find a latest build to verify.

Comment 21 cqu 2022-04-22 09:10:45 UTC

This issue is fixed by 2.5.0-DOWNSTREAM-2022-04-20-06-50-05， close it.