[DOC] Server UUID Setting (#128399) (#131846)

The `server.uuid` setting MUST be a valid UUIDv4.
Also, the setting was added in the middle of other SSL settings and it was misleading (due to a banner related to SSL settings).

(cherry picked from commit 9a34c20ace)

Co-authored-by: Luca Belluccini <luca.belluccini@elastic.co>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
This commit is contained in:
Kaarina Tungseth 2022-05-17 14:04:04 -05:00 committed by GitHub
parent 88e2372a60
commit d75e90ed38
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -569,6 +569,9 @@ all http requests to https over the port configured as `server.port`.
| An array of supported protocols with versions.
Valid protocols: `TLSv1`, `TLSv1.1`, `TLSv1.2`. *Default: TLSv1.1, TLSv1.2*
|[[server-uuid]] `server.uuid:`
| The unique identifier for this {kib} instance. It must be a valid UUIDv4. It gets automatically generated on the first startup if not specified and persisted in the `data` path.
| [[settings-xsrf-whitelist]] `server.xsrf.whitelist:`
| It is not recommended to disable protections for
arbitrary API endpoints. Instead, supply the `kbn-xsrf` header.