# Shield: wildcart deletes **URL:** \ **Category:** Elasticsearch\ **Created:** [March 5, 2015, 11:41am UTC](https://discuss.elastic.co/t/shield-wildcart-deletes/22527 "2015-03-05T11:41:50Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Jettro\_Coenradie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jettro_coenradie/32/59704_2.png) [@Jettro\_Coenradie](https://discuss.elastic.co/u/Jettro_Coenradie)\ **Post date:** [March 5, 2015, 11:41am UTC](https://discuss.elastic.co/t/shield-wildcart-deletes/22527/1 "2015-03-05T11:41:50Z")
Hi I am running the following code to remove indexes, if there is no index with the specified pattern, a shield enabled cluster throws an exception. To my opinion I have marked the options in a way that this should not happen. If I use the same code on a cluster without shield enabled, everything works fine. ``` client.admin().indices().prepareDelete(this.index + "*") .setIndicesOptions(IndicesOptions.fromOptions(true, true, ``` true, false)).get(); Is this an issue with Shield? The user I provide has admin rights. thanks -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/2a289411-e436-45b6-8f26-1ba8fce38aaf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2a289411-e436-45b6-8f26-1ba8fce38aaf%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![uboness1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/uboness1/32/849_2.png) [@uboness1](https://discuss.elastic.co/u/uboness1)\ **Post date:** [March 5, 2015, 12:18pm UTC](https://discuss.elastic.co/t/shield-wildcart-deletes/22527/2 "2015-03-05T12:18:37Z")
Hey Jettro, Indeed with shield the behaviour of the cluster when it comes to wildcards is a bit different. While with vanilla elasticsearch, we expand wildcards based on the index options, with shield we take the security context into account and only expand to those indices the user has privileges on. see: > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. and > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. On Thursday, March 5, 2015 at 12:41:50 PM UTC+1, Jettro Coenradie wrote: > Hi I am running the following code to remove indexes, if there is no index > with the specified pattern, a shield enabled cluster throws an exception. > To my opinion I have marked the options in a way that this should not > happen. If I use the same code on a cluster without shield enabled, > everything works fine. > > ``` > client.admin().indices().prepareDelete(this.index + "*") > .setIndicesOptions(IndicesOptions.fromOptions(true, true, > > ``` > > true, false)).get(); > > Is this an issue with Shield? The user I provide has admin rights. > > thanks -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5b7a659a-0e71-40ee-a4d9-7e2ef1c59b9a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5b7a659a-0e71-40ee-a4d9-7e2ef1c59b9a%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jettro\_Coenradie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jettro_coenradie/32/59704_2.png) [@Jettro\_Coenradie](https://discuss.elastic.co/u/Jettro_Coenradie)\ **Post date:** [March 19, 2015, 9:58pm UTC](https://discuss.elastic.co/t/shield-wildcart-deletes/22527/3 "2015-03-19T21:58:33Z")
Thanks Uri, like the documentation mentiones: Elasticsearch clusters with the Shield security plugin installed do not > honor the ignore\_unavailable option. Op donderdag 5 maart 2015 13:18:37 UTC+1 schreef uboness: > Hey Jettro, > > Indeed with shield the behaviour of the cluster when it comes to wildcards > is a bit different. While with vanilla elasticsearch, we expand wildcards > based on the index options, with shield we take the security context into > account and only expand to those indices the user has privileges on. see: > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/shield/current/limitations.html#_changes_in_index_wildcard_behavior) > > and > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/shield/current/securing-aliases.html) > > On Thursday, March 5, 2015 at 12:41:50 PM UTC+1, Jettro Coenradie wrote: > > > Hi I am running the following code to remove indexes, if there is no > > index with the specified pattern, a shield enabled cluster throws an > > exception. To my opinion I have marked the options in a way that this > > should not happen. If I use the same code on a cluster without shield > > enabled, everything works fine. > > > > ``` > > client.admin().indices().prepareDelete(this.index + "*") > > .setIndicesOptions(IndicesOptions.fromOptions(true, true, > > > > ``` > > > > true, false)).get(); > > > > Is this an issue with Shield? The user I provide has admin rights. > > > > thanks -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/c463934f-fc49-445d-a5c0-ae5fecd8751b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c463934f-fc49-445d-a5c0-ae5fecd8751b%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:25am UTC](https://discuss.elastic.co/t/shield-wildcart-deletes/22527/4 "2017-07-06T00:25:27Z")