-
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
Unable to skip untrusted certificate on minikube/Chrome #21074
Comments
@benoitf can you confirm that you have that on a private browser tab? And that happens before you authenticate with Dex right? |
yes it happens on all Chrome tabs afa3OgcroY.mp4I just installed che on minikube with chectl and I'm clicking on the dashboard link, that's all |
retried using latest minikube version (1.25.1)
So I still have proceed option on dashboard but not on dex tApiZmtfgR.mp4 |
I can open https://192.168.64.81.nip.io/plugin-registry/v3/ (with proceed option) or https://192.168.64.81.nip.io/devfile-registry/ but not the https://dex.192.168.64.81.nip.io page |
@sparkoo @skabashnyuk do you have any clue? |
I don't know why it is the case for dex. Maybe different kind of certificate? Different way how we use it in ingress? |
I confirm that I can reproduce the problem on macOS with Chrome but not with Firefox. |
@tolusha I have removed the sprint/current label and removed the milestone. Feel free to add a milestone if you plan to work on it during this sprint. |
Describe the bug
Usually, when browsing into an untrusted website, we can add exception to the website in advanced menu
But with Che/minikube, there is no such option, we have a message
Che version
next (development version)
Steps to reproduce
with Firefox I can add an exception and continue but not anymore with Chrome
Expected behavior
Be able to bypass untrusted certificate warning from the browser without adding certificates to the truststore
Runtime
minikube
Screenshots
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: