Steps to reproduce the issue
Use kibana config for Enterprise:
For example:
readonlyrest_kbn.login_html_head_inject
Expected result:
The trial version will start and later I can put my license there.
Or
The key is in the index so you can do the activation using Elasticsearch. So that Elasticsearch creates a license index.
Actual Result:
Kibana does not start:
[14:09:23:719] [error][plugins][ReadonlyREST][ConfigurationCompliance] FATAL: Current Activation Key is for a “Free” license. Your kibana.yml enables features that are not available at this subscription level. You can upgrade to an Enterprise license at https://readonlyrest.com
[14:09:23:719] [error][plugins][ReadonlyREST][ConfigurationCompliance] “Custom CSS/JS Injections” is only available for Enterprise subscribers.
[14:09:23:719] [error][plugins][ReadonlyREST][ConfigurationCompliance] “Login page customizations” is only available for PRO and Enterprise subscribers.
Thanks for the message. We will discuss internally what can we do with this case. For now, as a workoariound it seems that you can set activation key as environment variable before Kibana start, and then, load activation key via GUI.
Yes, but the key does not work when launched via systemd.
Need to go to the folder /usr/share/kibana => launch kibana => put the key in the index => terminate kibana => launch kibana via systemd.
And repeat this 3 times, since we usually use 1 server for 3 different clusters.
I would like to simplify the kibana installation process.
I hope you can do it.
“Custom CSS/JS Injections” is only available for Enterprise subscribers.