-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
GitHub OAuth flow is going into infinite loop if wrong configuration #21077
Comments
@ibuziuk @olexii4 @akurinnoy I am setting that as a blocker as it looks like it's not possible to use Che with private repositories anymore. |
Thanks for reporting. @vinokurig is it reproducible against the dogfooding instance for you, since I was not able to repro? |
Closing as it was a problem on my side. Wrong copy paste :) |
I think that even if oAuth is not configured properly Dashboard should display an error and not goes into an infinite loop |
Describe the bug
After setup the GitHub oAuth provider and using a factory with private repo browser goes into a refresh loop.
Che version
next (development version)
Steps to reproduce
screencast-nimbus-capture-2022.01.26-17_13_02.mp4
Expected behavior
Workspace should start.
Runtime
minikube
Screenshots
No response
Installation method
chectl/next
Environment
macOS
Eclipse Che Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: