No kibana index from headers / User's kibana index issue


(Asa Zalles-Milner) #22

etting active api to [es_5_0]
/api/saved_objects/?type=index-pattern&per_page=10000:1 Failed to load resource: the server responded with a status of 403 (Forbidden)
4commons.bundle.js?v=15647:38 Error: forbidden: [undefined] forbidden
at kibana.bundle.js?v=15647:228
at processQueue (commons.bundle.js?v=15647:38)
at commons.bundle.js?v=15647:38
at Scope.$eval (commons.bundle.js?v=15647:39)
at Scope.$digest (commons.bundle.js?v=15647:39)
at Scope.$apply (commons.bundle.js?v=15647:39)
at done (commons.bundle.js?v=15647:37)
at completeRequest (commons.bundle.js?v=15647:37)
at XMLHttpRequest.xhr.onload (commons.bundle.js?v=15647:37)


(Simone Scarduzio) #23

OK… What about Elasticsearch log?


(Asa Zalles-Milner) #24

The only forbiddens i am seeing in the elasticsearch log that kibana is talking to is the USR:[no basic auth header] where there is no username being provided.


(Simone Scarduzio) #25

Are you are missing some configuration in kibana.yml?

i.e.

elasticsearch.username

elasticsearch.password


(Asa Zalles-Milner) #26

Nothing has changed in the readonlyrest or kibana.yml, i also did not make the changes you reccomended to the readonlyrest ACL, and now I can’t access the plugin to do so.


(Simone Scarduzio) #27

What is the full log line?


(Simone Scarduzio) #28

Consider that the use of the credentials is not even ROR code, it’s Kibana code. How does it not even read that configuration?


(Simone Scarduzio) #29

This case was solved, there were problems with the plugin installation process in Kibana 5.6.1, a clean uninstall and reinstall of the plugin solved the issue