-
Notifications
You must be signed in to change notification settings - Fork 344
Shield being installed in the wrong directory #79
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
Comments
Hi This is not working with given workaround also its throwing an authentication error {"error":{"root_cause":[{"type":"security_exception","reason":"unable to authenticate user [esuser] for REST request [/]","header":{"WWW-Authenticate":"Basic realm="shield""}}],"type":"security_exception","reason":"unable to authenticate user [esuser] for REST request [/]","header":{"WWW-Authenticate":"Basic realm="shield""}},"status":401} I checked user and every thing seems fine |
I was able to use this fix and it worked, only thing this time around i did was used above docker file as mentioned by William, Earlier i was using the standard elastic search docker file which had step from java installation and installing elastic search binary, then added plugins installation, I wonder why didn't that work. as in above docker file we are extending the same standard elastic search docker file |
I may be seeing the same issue |
I have the same issue. And the "fix" of moving
|
Guys, the same problem and the same workaround works for me! |
+1 same issue, workaround didn't work for me for x-pack |
Moving the shield directory worked fine for me (using
|
mount the config dir both to the docker run -d \
-v /path/to/config:/etc/elasticsearch \
-v /path/to/config:/usr/share/elasticsearch/config \
elasticsearch:2 |
Will this workaround work if you want to create a new user after you have moved your shield files to /usr/share/elasticsearch/config/shield |
This image is officially deprecated in favor of upstream's images (see https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html). For more information, please see #160, docker-library/docs#842, and docker-library/docs#945.
Thanks! |
This commit was created by the elastic-dockerfiles-publisher.
This may be a shield issue. After several hours trying to figure out why authentication wasn't working, I noticed there are two config directories in my elasticsearch container. The shield data files are installed in
/etc/elasticsearch
but they need to be in/usr/share/elasticsearch/config/
.To solve this I moved the shield directory to the right location. Wondering if there is a better solution…
The text was updated successfully, but these errors were encountered: