You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's clarify xpack.security.http.ssl.client_authentication: optional recommendation for Kibana in 6.4+ directly in documentation.
We currently briefly mention this in the release notes of 6.4.0 (https://www.elastic.co/guide/en/kibana/6.4/release-notes-6.4.0.html). This is easy to miss and it doesn't help users who are running post-6.4.0 to begin with (or users upgrading from pre-6.3 and not reading the details in the readme).
No longer sets certs and keys for proxied calls to Elasticsearch #17804
Resolved issue with using PKI to authenticate the internal server user against Elasticsearch when X-Pack security is disabled or the realms in Elasticsearch are configured with PKI taking precedence to basic authentication.
Would like to see this documented directly in the appropriate sections around setting up security:
When setting up Elasticsearch https and not using PKI realm, do not set xpack.security.http.ssl.client_authentication: required. Recommended: xpack.security.http.ssl.client_authentication: optional
If there is a requirement for Kibana server to authenticate with Elasticsearch, configure PKI realm in Elasticsearch, then you can use elasticsearch.ssl.certificate and elasticsearch.ssl.key settings in the kibana.yml to specify the certificates to authenticate with Elasticsearch.
The text was updated successfully, but these errors were encountered:
Note that with server.ssl.clientAuthentication set to required, users are asked to provide a valid client certificate, even if they want to authenticate with username and password. Depending on the security policies, it may or may not be desired. If not, server.ssl.clientAuthentication can be set to optional. In this case, Kibana still requests a client certificate, but the client won’t be required to present one. The optional client authentication mode might also be needed in other cases, for example, when PKI authentication is used in conjunction with Reporting.
Let's clarify
xpack.security.http.ssl.client_authentication: optional
recommendation for Kibana in 6.4+ directly in documentation.We currently briefly mention this in the release notes of 6.4.0 (https://www.elastic.co/guide/en/kibana/6.4/release-notes-6.4.0.html). This is easy to miss and it doesn't help users who are running post-6.4.0 to begin with (or users upgrading from pre-6.3 and not reading the details in the readme).
Would like to see this documented directly in the appropriate sections around setting up security:
xpack.security.http.ssl.client_authentication: required
. Recommended:xpack.security.http.ssl.client_authentication: optional
elasticsearch.ssl.certificate
andelasticsearch.ssl.key
settings in the kibana.yml to specify the certificates to authenticate with Elasticsearch.The text was updated successfully, but these errors were encountered: