This is my user's privileges { "cluster" : [ "all" ], "global" : [ ], "indices" : [ { "names" : [ "*" ], "privileges" : [ "all" ], "allow_restricted_indices" : true } ], "applications" : [ { "application" : "*", "…

[image] panagiss: "There are no external requests known to support wildcards that don't support replacing their indices" This message has been improved in more recent versions of Elasticsearch. It typically means that you're passing a wildcard (*) to the get API (e.g. GET /metricbeat-*/_doc/1)…

Thanks! So i cannot specify wildcards in the URL path for indices ever, right?

Hi @panagiss To be more precise you can not use * when you are doing a GET by document _id, you can't use a wildcard with when searching by _id you must provide the individual index (or alias) Incorrect Syntax GET /filebeat-*/_doc/1JbB83oBFS-aXHYZYwPk Correct Syntax GET /filebeat-7.13.4-2021.07…

Superuser doesn't have access to read a document?

Elastic Stack Elasticsearch

TimV (Tim Vernum) August 1, 2021, 12:20pm 2

This message has been improved in more recent versions of Elasticsearch. It typically means that you're passing a wildcard (*) to the get API (e.g. GET /metricbeat-*/_doc/1) which is not allowed.

Topic		Replies	Views
Authorization Exception for SuperUser Elasticsearch elastic-stack-security	6	2719	September 21, 2020
Getting unauthorized when doing GET on indices with a read-only user Kibana elastic-stack-security	4	3655	September 23, 2020
No 403 response if user is not allowed to read index Elasticsearch	3	748	May 23, 2017
Action indices:data/read/mget is unauthorized but privilege listed Elasticsearch elastic-stack-security	31	13592	July 6, 2017
Check access to a document Elasticsearch elastic-stack-security	2	427	January 13, 2020

Superuser doesn't have access to read a document?

Related topics