Hello, I am using Kibana/Elasticsearch 7.9.0, and testing enabling security on the stack. I am starting with a test user that gets the following on the GET API call: GET _cat/indices { "error" : { "root_cause" : [ { "type" : "security_exception", "reason" : "action [i…

Awesome, thank you, that fixed it. What should I do with this one with 403 on the filebeat-* index-pattern? I do not get it for the apm-* index pattern: {"type":"response","@timestamp":"2020-08-24T15:05:39Z","tags":[],"pid":45,"method":"put","statusCode":403,"req":{"url":"/api/saved_objects/index-…

cotjoey (Joey) August 26, 2020, 8:07pm 4

I fixed my 2nd question in this post:

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Getting unauthorized when doing GET on indices with a read-only user