2018-12-20 08:04:54 -05:00
[[ingest-node-set-security-user-processor]]
2020-08-12 11:49:54 -04:00
=== Set security user processor
++++
<titleabbrev>Set security user</titleabbrev>
++++
2020-02-11 07:05:01 -05:00
Sets user-related details (such as `username`, `roles`, `email`, `full_name`,
`metadata`, `api_key`, `realm` and `authentication_type`) from the current
2018-12-20 08:04:54 -05:00
authenticated user to the current document by pre-processing the ingest.
2020-02-11 07:05:01 -05:00
The `api_key` property exists only if the user authenticates with an
API key. It is an object containing the `id` and `name` fields of the API key.
The `realm` property is also an object with two fields, `name` and `type`.
When using API key authentication, the `realm` property refers to the realm
from which the API key is created.
The `authentication_type` property is a string that can take value from
`REALM`, `API_KEY`, `TOKEN` and `ANONYMOUS`.
2018-12-20 08:04:54 -05:00
IMPORTANT: Requires an authenticated user for the index request.
[[set-security-user-options]]
.Set Security User Options
[options="header"]
|======
2020-02-11 07:05:01 -05:00
| Name | Required | Default | Description
| `field` | yes | - | The field to store the user information into.
| `properties` | no | [`username`, `roles`, `email`, `full_name`, `metadata`, `api_key`, `realm`, `authentication_type`] | Controls what user related properties are added to the `field`.
2018-12-20 08:04:54 -05:00
include::common-options.asciidoc[]
|======
The following example adds all user details for the current authenticated user
to the `user` field for all documents that are processed by this pipeline:
[source,js]
--------------------------------------------------
{
"processors" : [
{
"set_security_user": {
"field": "user"
}
}
]
}
--------------------------------------------------
// NOTCONSOLE