I am currently trying to amend the rule, and I encountered a problem on fail to load the configuration.
Elasticsearch version: 5.6.1
kibana version : 5.6.1
ROR Pro version : 1.16.11
Both my es & kibana run as service in centos
I am still in the testing stage and use auth key directly on the access_control rule.
My steps are as follow
- amend the elasticsearh.yml
- restart elasticsearch as a service
- try to enter kibana with the saved credentials / try to enter curl elasticsearch with saved credentials
-> both failed
- name: "::GROUPA::" auth_key: delete:changeme kibana_access: rw actions: ["indices:data/read/*", "indices:data/write/*"] indices: [".kibana", ".kibana-devnull", "logstash-*"] kibana_hide_apps: ["readonlyrest_kbn", "timelion", "kibana:dev_tools", "kibana:management"]
The reason what I would like to create this admin because I want to perform deletion on the dashboard and also execute the curl in dev_tools. becuse even i use admin account, i cannot perform delete action on kibana objects.