-
Notifications
You must be signed in to change notification settings - Fork 890
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
logout tab is not working #2895
Comments
Did this happen in RC1 as well? |
Hi @juliusvonkohout , |
@thesuperzapper do you know about this? I think we had and fixed this problem before. Could it be that we need to merge kubeflow/kubeflow#7631 and that there was a hotfix in kubeflow/manifest as well? @tarekabouzeid @muratyarali can you apply the patch and check whether it should be oauth2/logout or oauth2/sign_out? |
@juliusvonkohout we actually just need to change the central dashboard so that it uses a GET request (with a basic |
@thesuperzapper can you patch this then in kubeflow/kubeflow and sent me a tag for synchronization? Nevertheless i still do not like oauth2/logout vs. oauth2/sign_out and will remove one of them. |
CC also @kromanow94 @MaxKavun |
Hey, @MaxKavun and my expertise resolves mostly around backend. But, with some guidance, we can provide help. Let us know if this is something you're interested in. |
We should also extend the test here to cover this https://github.com/kubeflow/manifests/blob/master/.github/workflows/dex_test.yaml. |
An there is also kubeflow/kubeflow#7624 for reference |
And another one kubeflow/dashboard#57 |
As I was saying in #2895 (comment). If anyone wants to raise a PR on the central dashboard in the |
Validation Checklist
Version
1.9
Describe your issue
I recently installed Kubeflow v1.9.1-RC.2, and the logout tab on the Kubeflow UI is unresponsive. Clicking it does nothing, but reloading the page takes me to the login page.
Steps to reproduce the issue
2.Reload the page and go to the login page
Put here any screenshots or videos (optional)
No response
The text was updated successfully, but these errors were encountered: