-
Notifications
You must be signed in to change notification settings - Fork 25k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-wildcard index deletion returns a wildcard warning with security enabled #67958
Comments
Pinging @elastic/es-security (Team:Security) |
A pretty large stack trace
|
It appears that this problem occurs because when we resolve index names at the security layer, in It seems to me that making |
Fixed by #68021 |
Description of the problem including expected versus actual behavior
@spalger discovered this issue while doing some testing around the
action.destructive_requires_name
setting: #66908 (comment)In short, if you run Elasticsearch with security enabled and
action.destructive_requires_name
set totrue
, and you're ignoring unavailable indices, you can get a wildcard warning from an index deletion request that doesn't include a wildcard.This reproduces on 7.10.2 and master for me.
Steps to reproduce
Reproducing on the command line of a fresh 7.10.2 installation:
xpack.security.enabled: true
andaction.destructive_requires_name
toconfig/elasticsearch.yml
.elastic
user to `changeme.Reproducing using a YAML test:
rest-api-spec/src/main/resources/rest-api-spec/test/indices.delete/20_destructive_wildcard.yml
./gradlew :rest-api-spec:yamlRestTest -Dtests.method="test {yaml=indices.delete/20*}"
The text was updated successfully, but these errors were encountered: