Typo in security recommendation
This commit is contained in:
parent
3f7f651619
commit
187bccec6b
|
@ -87,7 +87,7 @@ kibana_user:
|
|||
|
||||
Hidden resources are automatically reserved.
|
||||
|
||||
To add or remove these flags, you need to modify `plugins/opensearch-security/securityconfig/internal_users.yml` and run `plugins/opensearch-security/tools/securityadmin.sh`.
|
||||
To add or remove these flags, modify `plugins/opensearch-security/securityconfig/internal_users.yml` and run `plugins/opensearch-security/tools/securityadmin.sh`.
|
||||
|
||||
|
||||
---
|
||||
|
|
|
@ -12,7 +12,7 @@ The security plugin includes an internal user database. Use this database in pla
|
|||
|
||||
Roles are the core way of controlling access to your cluster. Roles contain any combination of cluster-wide permissions, index-specific permissions, document- and field-level security, and tenants. Then you map users to these roles so that users gain those permissions.
|
||||
|
||||
Unless you need to create new [read-only or hidden users]({{site.url}}{{site.baseurl}}/security-plugin/access-control/api#read-only-and-hidden-resources), we **highly** recommend using OpenSearch Dashboards or the REST API to create new users, roles, and role mappings. The `.yml` files are for initial setup, not ongoing use.
|
||||
Unless you need to create new [reserved or hidden users]({{site.url}}{{site.baseurl}}/security-plugin/access-control/api#read-only-and-hidden-resources), we **highly** recommend using OpenSearch Dashboards or the REST API to create new users, roles, and role mappings. The `.yml` files are for initial setup, not ongoing use.
|
||||
{: .warning }
|
||||
|
||||
---
|
||||
|
|
Loading…
Reference in New Issue