Console 5.0.0-rc1 cannot verify ES certificate with xpack security installed

[mike-mosher]

Kibana version: 5.0.0-rc1

Elasticsearch version: 5.0.0-rc1

Server OS version: Windows 2012R2 64-bit

Browser version: Chrome Version 53.0.2785.143

Browser OS version: Windows 10 64-bit

Original install method (e.g. download page, yum, from source, etc.): download page

Description of the problem including expected versus actual behavior:

Testing the new 5.0.0-rc1 stack and want to use Console (formerly Sense). I have xpack security installed and configured on the ES cluster.

When I try to run a command using Console, I get the following error:

Error connecting to '<server>':

Client request error: self signed certificate in certificate chain

In 2.4 with Shield installed, I had to add the following to kibana.yml:

sense.proxyConfig:
  - match:
      host: "*"
    ssl:
      ca: /path/to/cacert.pem

  - match:
      protocol: "https"
    ssl:
      verify: true

There have been alot of setting changes with the move to xpack in 5.0.0. I have tried to search the docs endlessly for any reference to theses settings or to Console / Sense, and only found a reference to sense.proxyFilter here: https://www.elastic.co/guide/en/kibana/5.0/securing_console.html

Also, some of the documentation seems incorrect: https://www.elastic.co/guide/en/kibana/5.0/console-kibana.html makes reference to the ability to set the server in Console, which does not seem to be possible in 5.0.0-rc1

[thomasneirynck]

Hi @mike-mosher

Can you try replacing all sense.* configuration settings in your .yml files with console.*? The application has been renamed for the 5 release.

Thanks, indeed, the docs seem out-of-date. This will need to be addressed for the final 5.0 release.

[mike-mosher]

That did it. I probably should have guessed that change. thank you for the help.

Also, seems that "defaultServerUrl" is a depreciated setting.