Skip to content

Commit d52d003

Browse files
authored
[DOCS] Mention that inline scripts need to be enabled for Kibana (#60633) (#60797)
1 parent eabdcb7 commit d52d003

File tree

1 file changed

+11
-4
lines changed

1 file changed

+11
-4
lines changed

docs/reference/scripting/security.asciidoc

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -78,10 +78,16 @@ security of the Elasticsearch deployment.
7878
[discrete]
7979
=== Allowed script types setting
8080

81-
By default all script types are allowed to be executed. This can be modified using the
82-
setting `script.allowed_types`. Only the types specified as part of the setting will be
83-
allowed to be executed. To specify no types are allowed, set `script.allowed_types` to
84-
be `none`.
81+
Elasticsearch supports two script types: `inline` and `stored` (<<modules-scripting-using>>).
82+
By default, {es} is configured to run both types of scripts.
83+
To limit what type of scripts are run, set `script.allowed_types` to `inline` or `stored`.
84+
To prevent any scripts from running, set `script.allowed_types` to `none`.
85+
86+
IMPORTANT: If you use {kib}, set `script.allowed_types` to `both` or `inline`.
87+
Some {kib} features rely on inline scripts and do not function as expected
88+
if {es} does not allow inline scripts.
89+
90+
For example, to run `inline` scripts but not `stored` scripts, specify:
8591

8692
[source,yaml]
8793
----
@@ -90,6 +96,7 @@ script.allowed_types: inline <1>
9096
<1> This will allow only inline scripts to be executed but not stored scripts
9197
(or any other types).
9298

99+
93100
[[allowed-script-contexts-setting]]
94101
[discrete]
95102
=== Allowed script contexts setting

0 commit comments

Comments
 (0)