Issues with deleting index with wildcards

Search Guard
1

Search Guard Version 5.2.2

User have sgamin_all_access:

sg_all_access:

cluster:

  • “*”

indices:

‘*’:

‘*’:

  • “*”

When I tried to delete indices using wildcards, etc. https://hostname:9200/test*:

  • if there are matching indices, the operation goes through

  • if there are no matching indices, search guard throws the error:

Type: security_exception

Reason: “no permissions for indices:admin/delete”

This is very misleading. On the other hand, if you look at behavior in Elasticsearch without search guard, the delete operation goes through whether there are matching indices or not.

Is this a misconfiguration on my part, or is this a bug?

2

good catch, thx

can you file an issue in github?

···

On Thursday, 13 April 2017 22:32:21 UTC+2, Daphne Ng wrote:

Search Guard Version 5.2.2

User have sgamin_all_access:

sg_all_access:

cluster:

  • “*”

indices:

‘*’:

‘*’:

  • “*”

When I tried to delete indices using wildcards, etc. https://hostname:9200/test*:

  • if there are matching indices, the operation goes through
  • if there are no matching indices, search guard throws the error:

Type: security_exception

Reason: “no permissions for indices:admin/delete”

This is very misleading. On the other hand, if you look at behavior in Elasticsearch without search guard, the delete operation goes through whether there are matching indices or not.

Is this a misconfiguration on my part, or is this a bug?

3

Sure, https://github.com/floragunncom/search-guard/issues/332.

···

On Saturday, April 15, 2017 at 4:30:31 PM UTC-4, Search Guard wrote:

good catch, thx

can you file an issue in github?

On Thursday, 13 April 2017 22:32:21 UTC+2, Daphne Ng wrote:

Search Guard Version 5.2.2

User have sgamin_all_access:

sg_all_access:

cluster:

  • “*”

indices:

‘*’:

‘*’:

  • “*”

When I tried to delete indices using wildcards, etc. https://hostname:9200/test*:

  • if there are matching indices, the operation goes through
  • if there are no matching indices, search guard throws the error:

Type: security_exception

Reason: “no permissions for indices:admin/delete”

This is very misleading. On the other hand, if you look at behavior in Elasticsearch without search guard, the delete operation goes through whether there are matching indices or not.

Is this a misconfiguration on my part, or is this a bug?