Skip to content

Commit d58e7eb

Browse files
[DOC] Server UUID Setting (elastic#128399) (elastic#131177)
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 9a34c20) Co-authored-by: Luca Belluccini <[email protected]>
1 parent 4bdb546 commit d58e7eb

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

docs/setup/settings.asciidoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -608,6 +608,9 @@ all http requests to https over the port configured as <<server-port, `server.po
608608
| An array of supported protocols with versions.
609609
Valid protocols: `TLSv1`, `TLSv1.1`, `TLSv1.2`, `TLSv1.3`. *Default: TLSv1.1, TLSv1.2, TLSv1.3*
610610

611+
|[[server-uuid]] `server.uuid:`
612+
| 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.
613+
611614
| [[settings-xsrf-allowlist]] `server.xsrf.allowlist:`
612615
| It is not recommended to disable protections for
613616
arbitrary API endpoints. Instead, supply the `kbn-xsrf` header.

0 commit comments

Comments
 (0)