Skip to content
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

My daily authentication dance #21352

Closed
Tracked by #21351
l0rd opened this issue Apr 26, 2022 · 2 comments · Fixed by eclipse-che/che-operator#1379
Closed
Tracked by #21351

My daily authentication dance #21352

l0rd opened this issue Apr 26, 2022 · 2 comments · Fixed by eclipse-che/che-operator#1379
Assignees
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/next

Comments

@l0rd
Copy link
Contributor

l0rd commented Apr 26, 2022

Describe the bug

On Che dogfooding instance I get a 403 error once every day when my token expires and I am redirected to OpenShift authentication page. And, after re-logging in, I am not redirected to the dashboard but to the OpenShift authentication page and I need to edit the URL to get back to the dashboard.

dogfooding-auth-problem

Che version

next (development version)

Steps to reproduce

Wait for the authentication token to expire (24h) and click on a link on the dashboard or refresh the page.

Expected behavior

After logging in I expect to be redirected to the dashboard instead of seeing a 403 error.
And after logging in the second time I expect to be redirected to the dashboard too.

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

other (please specify in additional context)

Eclipse Che Logs

No response

Additional context

After trying too many times to login I get this error too:

image

image

@l0rd l0rd added the kind/bug Outline of a bug - must adhere to the bug report template. label Apr 26, 2022
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Apr 26, 2022
@ibuziuk ibuziuk added sprint/next severity/P1 Has a major impact to usage or development of the system. area/dashboard and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Apr 27, 2022
@ibuziuk ibuziuk mentioned this issue Apr 27, 2022
58 tasks
@olexii4 olexii4 self-assigned this Apr 27, 2022
@nickboldt
Copy link
Contributor

Note: This problem has been reported against Che 7.46.x / Dev Spaces 3.0 ER too, not just in :next

@dmytro-ndp
Copy link
Contributor

dmytro-ndp commented Apr 27, 2022

@l0rd, @nickboldt: I can confirm, that the problem described in issue has been reproduced in Dev Spaces 3.0.0 ER as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/next
Projects
None yet
6 participants