-
Notifications
You must be signed in to change notification settings - Fork 8
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
ElasticsearchException[Security configuration cannot be loaded for unknown reasons #21
Comments
Debug log:
|
Populating /ac/ac data translates to another error:
|
"_all" access (that you try to address by issiueing only a _search request) is forbidden for any user (even admin in your case), you will have to specify a proper indice to make it work. For your configuration errors, they come indeed from the fact that you didn't populate /armor/ac/ac before |
Something is odd, here is my /armor/ac/ac config:
Here is elasticsearch.yml (armor portion):
Here is my request and response as admin:
And here is my request and response as kibana-user
I have tried following armor/ac/ac configuration as well with the same result:
What am I missing in the configurations? |
Hello @vkhazin , Your configuration is malformed (didn't check the documentation but maybe it's misleading) You declare two restactionfilter but instead configure two requestactionfilter. They are not equivalent. Restaction filter allow someone to block a request that is made from Rest and Request Action Filter blocks both a Rest Request and Transport Request. That the one you want to use if you use it.
|
Hey @jehuty0shift, Thank you for your comments!
with the same results as for 'admin':
|
curl -v http://app.user:***@localhost:9200/_search?pretty=true
elasticsearch.yml configurations
There is no localhost:9200/ac index present at the time of testing, adding the default settings did not seem to have any impact:
Root level request seems to succeed:
The text was updated successfully, but these errors were encountered: