This commit is contained in:
parent
0286d0a769
commit
063518ca2b
|
@ -78,10 +78,16 @@ security of the Elasticsearch deployment.
|
|||
[discrete]
|
||||
=== Allowed script types setting
|
||||
|
||||
By default all script types are allowed to be executed. This can be modified using the
|
||||
setting `script.allowed_types`. Only the types specified as part of the setting will be
|
||||
allowed to be executed. To specify no types are allowed, set `script.allowed_types` to
|
||||
be `none`.
|
||||
Elasticsearch supports two script types: `inline` and `stored` (<<modules-scripting-using>>).
|
||||
By default, {es} is configured to run both types of scripts.
|
||||
To limit what type of scripts are run, set `script.allowed_types` to `inline` or `stored`.
|
||||
To prevent any scripts from running, set `script.allowed_types` to `none`.
|
||||
|
||||
IMPORTANT: If you use {kib}, set `script.allowed_types` to `both` or `inline`.
|
||||
Some {kib} features rely on inline scripts and do not function as expected
|
||||
if {es} does not allow inline scripts.
|
||||
|
||||
For example, to run `inline` scripts but not `stored` scripts, specify:
|
||||
|
||||
[source,yaml]
|
||||
----
|
||||
|
@ -90,6 +96,7 @@ script.allowed_types: inline <1>
|
|||
<1> This will allow only inline scripts to be executed but not stored scripts
|
||||
(or any other types).
|
||||
|
||||
|
||||
[[allowed-script-contexts-setting]]
|
||||
[discrete]
|
||||
=== Allowed script contexts setting
|
||||
|
|
Loading…
Reference in New Issue