mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 17:28:26 -04:00
[DOC] Server UUID Setting (#128399)
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).
This commit is contained in:
parent
ef6a4e4498
commit
9a34c20ace
1 changed files with 3 additions and 4 deletions
|
@ -543,10 +543,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]
|
||||
|
@ -627,6 +623,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.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue