You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2022. It is now read-only.
There's a confusing statement in the documentation of Open distro for ElasticSearch located at https://opendistro.github.io/for-elasticsearch-docs/docs/security/access-control/api/#update-configuration
The original text is as follows:
Creates or updates the existing configuration using the REST API rather than securityadmin.sh. This operation can easily break your existing configuration, so we recommend using securityadmin.sh instead. See Access control for the API for how to enable this operation.
In the first half of the paragraph the doc recommand us to use REST API and use securityadmin.sh in the rest of it.
Overall view of the full text, Using REST API should be recommanded.
The text was updated successfully, but these errors were encountered:
geek981108
added a commit
to geek981108/for-elasticsearch-docs
that referenced
this issue
May 17, 2021
Hi @geek981108, agreed that the wording is a bit confusing. For most things -- creating users, roles, etc. -- the REST API is the better way to go. For updating the configuration, though, the REST API is pretty risky. We even keep the request disabled by default. securityadmin.sh is much safer. I've tried to clarify a bit here: e24c6a7
There's a confusing statement in the documentation of Open distro for ElasticSearch located at
https://opendistro.github.io/for-elasticsearch-docs/docs/security/access-control/api/#update-configuration
The original text is as follows:
Creates or updates the existing configuration using the REST API rather than securityadmin.sh. This operation can easily break your existing configuration, so we recommend using securityadmin.sh instead. See Access control for the API for how to enable this operation.
In the first half of the paragraph the doc recommand us to use REST API and use securityadmin.sh in the rest of it.
Overall view of the full text, Using REST API should be recommanded.
The text was updated successfully, but these errors were encountered: