-
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
Improved messages for self-signed cert issues #15951
Conversation
Can one of the admins verify this patch? |
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) |
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) |
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) |
@l0rd @beaumorley Could you please validate the error message we provide. Maybe you have some suggestions. |
This comment has been minimized.
This comment has been minimized.
Well, there is no easy way to get CA by the end-user. It makes me think that it would be great if Che Server serves CA and gives users an ability to download it as a file. But I'm not sure if it's really secure thing to do. |
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) |
One simple thing I'd suggest is to change the text color on the error. The orange on black is hard to read. If you want to keep some orange to indicate that it is an important error, possibly just keep the headline orange? If this is a product wide convention to use orange, we may want to address it more holistically later but just wanted to bring it up. ** current error copy ** Probably, one of Che hosts is signed with a self-signed certificate. Possible solutions would be: Click here to reload page. ** first stab at suggested improvements to error copy *** Your Che host may be signed with a self-signed certificate. To resolve this issue, try these possible solutions: After trying each of these solutions, [refresh your Dashboard] (link) to see if the problem has been resolved If I have some of the troubleshooting wrong, let me know and I can try and tweak this. |
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) ℹ️ |
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) |
dashboard/src/components/branding/che-dashboard-configuration.service.ts
Outdated
Show resolved
Hide resolved
dashboard/src/app/organizations/organizations-config.service.spec.ts
Outdated
Show resolved
Hide resolved
This looks great. Very clear and easy to read. Thanks! |
Just had a thought on this new design. We need a close button or an X at the top right of the screen (next to the Certificate Error title). If the user does not want to do any of the suggested options they should have a way to just cancel. Sorry I missed this. I think it is pretty important to add. |
Signed-off-by: Oleksii Orel <oorel@redhat.com>
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) |
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) |
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) |
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) ℹ️ |
crw-ci-test |
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) |
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) |
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
Signed-off-by: Oleksii Orel oorel@redhat.com
What does this PR do?
Improved messages for the self-signed cert issue.
What issues does this PR fix or reference?
#15298
Release Notes
Docs PR