Error: Unable to connect to Elasticsearch when testing Kibana without production credentials

Answer

Kibana does not provide a setting for anonymous or trial‑license fallback connections to Elasticsearch. When xpack.security.enabled is true, Kibana always requires valid credentials and will show the “Unable to connect to Elasticsearch” error if they are missing.

Confirmed facts

• Kibana’s configuration reference contains no option to disable authentication or to enable a trial‑license mode for the Elasticsearch connection.
• The trial license in Elastic Stack applies to X‑Pack features on Elasticsearch, not to Kibana’s ability to connect without credentials.
• Elastic’s public roadmap (up to 8.x) does not list a credential‑less or anonymous connection mode for Kibana; security is treated as a core requirement.

Recommended steps for integration testing

1. If you can disable Elasticsearch security in your test cluster:
   • Set xpack.security.enabled: false in elasticsearch.yml.
   • Restart Elasticsearch.
   • Leave kibana.yml unchanged (or point elasticsearch.hosts to the test node).
   • Restart Kibana and verify that the login screen is bypassed and Discover/Visualize/Dashboards load.
2. If you must keep security enabled:
   • Create a dedicated test role with read‑only access to the .kibana* indices and any monitoring indices you need.
   • Create a user (or API key) assigned to that role.
   • Add the credentials to kibana.yml:

     elasticsearch.username: "test_user"
     elasticsearch.password: "test_password"

   • Restart Kibana and confirm that the UI features are enabled without the connection error.

Missing diagnostic detail

Can you disable Elasticsearch security in your test environment? If the answer is “no”, follow the test‑user approach above; if “yes”, the disabled‑security approach is simpler.