IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Security Settings in Kibana
editSecurity Settings in Kibana
editYou do not need to configure any additional settings to use X-Pack security in Kibana. It is enabled by default.
General Security Settings
edit-
xpack.security.enabled -
By default, Kibana automatically detects whether to enable the security features based on the license and whether Elasticsearch security features are enabled.
Do not set this to
false; it disables the login form, user and role management screens, and authorization using Kibana privileges. To disable security features entirely, see Elasticsearch security settings. -
xpack.security.audit.enabled -
Set to
trueto enable audit logging for security events. By default, it is set tofalse. For more details see Audit Logging. -
xpack.security.authorization.legacyFallback -
Set to
true(default) to enable the legacy fallback. See Authorization for more details.
User Interface Security Settings
editYou can configure the following settings in the kibana.yml file:
-
xpack.security.cookieName -
Sets the name of the cookie used for the session. The default value is
"sid" -
xpack.security.encryptionKey - An arbitrary string of 32 characters or more that is used to encrypt credentials in a cookie. It is crucial that this key is not exposed to users of Kibana. By default, a value is automatically generated in memory. If you use that default behavior, all sessions are invalidated when Kibana restarts.
-
xpack.security.secureCookies -
Sets the
secureflag of the session cookie. The default value isfalse. It is set totrueifserver.ssl.certificateandserver.ssl.keyare set. Set this totrueif SSL is configured outside of Kibana (for example, you are routing requests through a load balancer or proxy). -
xpack.security.sessionTimeout - Sets the session duration (in milliseconds). By default, sessions stay active until the browser is closed. When this is set to an explicit timeout, closing the browser still requires the user to log back in to Kibana.