github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 17:28:26 -04:00
Code Issues Projects Releases Packages Wiki Activity

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

Browse source 
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>
This commit is contained in:
Kibana Machine 2022-04-28 13:31:59 -05:00 • committed by GitHub
parent 30bb9ba2f8
commit be8602e755
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/setup/settings.asciidoc
View file

@ -539,10 +539,6 @@ inactive socket. *Default: `"120000"`*
| Paths to a PEM-encoded X.509 server certificate and its corresponding private key. These
are used by {kib} to establish trust when receiving inbound SSL/TLS connections from users.
|[[server-uuid]] `server.uuid:`
| The unique identifier for this {kib} instance.
|===
[NOTE]
@ -623,6 +619,9 @@ all http requests to https over the port configured as <<server-port, `server.po
| An array of supported protocols with versions.
Valid protocols: `TLSv1`, `TLSv1.1`, `TLSv1.2`, `TLSv1.3`. *Default: TLSv1.1, TLSv1.2, TLSv1.3*
|[[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-allowlist]] `server.xsrf.allowlist:`
| It is not recommended to disable protections for
arbitrary API endpoints. Instead, supply the `kbn-xsrf` header.