-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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 UI does not format proxy TLS config correctly #179269
Comments
Pinging @elastic/fleet (Team:Fleet) |
To be clear, we expect this certificate to be formatted with the |
@kpollich, not really. The issue here is that the certificate has 2 of its line on the same line. It should be formatted like that:
Besides I believe the ahgent receives it as json
So for the proxy, the field forces the whole text to be on a single line and I believe it's losing the correct line breaks. and it can be seen in the policy stored on
as well as in the yaml from View Policy on fleetUI:
|
Kibana version: 8.13, main
Elasticsearch version: 8.13, main
Server OS version: Elastic Cloud
Browser version: Brave v1.64.109 (Mar 20, 2024)
Browser OS version: Pop!_OS 22.04 LTS
Original install method (e.g. download page, yum, from source, etc.): N/A
Describe the bug: Fleet UI does not format proxy TLS config correctly
Steps to reproduce:
Expected behavior:
The TLS config should be correctly formatted as it happens for the ES output and others
Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context:
The text was updated successfully, but these errors were encountered: