Fleet Server Settings Elasticsearch CA Fingerprint Rejected

[ddth_2022 (Dev Dua)]

I tried entering the base64 encoded Fingerprint of the CA certificate in the Output section of Fleet settings, but I get the error below -

The string is most definitely base64 encoded. What can I do to get past this issue?

[ikakavas (Ioannis Kakavas)]

How did you get that value ? Is it actually the SHA256 fingerprint of a CA certificate ?

[ddth_2022 (Dev Dua)]

I used openssl x509 -fingerprint -sha256 -in ca.crt to get the fingerprint and then converted it to base64 (as required in the error message)

[nchaulet (Nicolas Chaulet)]

Hi @ddth_2022

Looks like we have a bug in the client validation of this form, I filled this issue on our side and this should be fixed in an upcoming version [Fleet] Output CATrustedFingerPrint validation client side is broken · Issue #125661 · elastic/kibana · GitHub

In the mean time to unlock you, you can edit this settings via the API

curl --request PUT \
  --url https://{KIBANA_HOST}/api/fleet/outputs/fleet-default-output  \
  --header 'kbn-xsrf: xxxx' \
  --data '{
	"name": "default",
	"type": "elasticsearch",
	"hosts": [
		"https://test.fr"
	],
	"is_default": true,
	"is_default_monitoring": true,
	"config_yaml": "#test",
	"ca_trusted_fingerprint": "yourfingerprint"
}'