You do not need to configure any additional settings to use the {security-features} in {kib}. They are enabled by default.
|
By default, {kib} automatically detects whether to enable the
{security-features} based on the license and whether {es} {security-features}
are enabled. |
|
Set to |
You can configure the following settings in the kibana.yml
file.
|
Sets the name of the cookie used for the session. The default value is |
|
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 {kib}. By default, a value is automatically generated in memory. If you use that default behavior, all sessions are invalidated when {kib} restarts. In addition, high-availability deployments of {kib} will behave unexpectedly if this setting isn’t the same for all instances of {kib}. |
|
Sets the |
|
Sets the session duration. By default, sessions stay active until the browser is closed. When this is set to an explicit idle timeout, closing the browser still requires the user to log back in to {kib}. |
Tip
|
The format is a string of |
|
Sets the maximum duration, also known as "absolute timeout". By default,
a session can be renewed indefinitely. When this value is set, a session will end
once its lifespan is exceeded, even if the user is not idle. NOTE: if |
Tip
|
The format is a
string of |
|
Adds a message to the login screen. Useful for displaying information about maintenance windows, links to corporate sign up pages etc. |