-
Notifications
You must be signed in to change notification settings - Fork 82
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
[Fleet] Improve error message for expired certificate authority #2447
Comments
Pinging @elastic/fleet (Team:Fleet) |
@kpollich Should we move this to fleet-server repo too? |
I think this one should stay in Kibana because we report the error message in the UI if I'm understanding the issue correctly. |
@kpollich My understanding of the SDH is that the error was reported in the CLI when attempting to set up the Fleet Server. There wouldn't be a way of auditing the certs on the Kibana side since the params point to directories on the host machine. |
Ah I misunderstood the initial SDH then. I'll transfer this now 😄 |
Created this PR that shows that the error message mentioned in this issue is most probably not due to an expired CA. |
Thanks Kaan, that PR demonstrates the specific error cases well. Appreciate you creating it and investigating here 🙏 The error messages in question come from Go's HTTP internals, and as such we don't really have a way to replace or improve them. I'm going to close this as not planned as a result. |
Currently, providing an expired certificate authority for Fleet Server, Logstash, etc will report a generic
Unknown Certificate Authority
error. It'd be ideal if we could detect the expiration case explicitly and provide a more specific error message.The text was updated successfully, but these errors were encountered: