🔐 Secure your cluster with TLS, numerous authentication backends, data masking, audit logging as well as role-based access control on indices, documents, and fields
Describe the bug
The code of this repository (see AuthTokenProcessorHandler:L354) and this comment suggest there is a JWT expiry setting. However, when setting it like below, it doesn't work (JWT expiry is still the default 60 * 60 seconds).
Describe the bug The code of this repository (see AuthTokenProcessorHandler:L354) and this comment suggest there is a JWT expiry setting. However, when setting it like below, it doesn't work (JWT expiry is still the default
60 * 60
seconds).config.yml
To Reproduce Steps to reproduce the behavior:
config.yml
of the security plugin to the contents shown abovesecurityadmin.sh
Expected behavior Setting
jwt.expiry
should change the TTL of the generated JWT.Host/Environment (please complete the following information):
opendistroforelasticsearch-kibana
): 1.13.2