The security mode has been enabled for the OpenSearch cluster.
Parameter |
Description |
---|---|
Permission |
Single permission, for example, creating an index (for example, indices:admin/create) |
Action group |
A group of permissions. For example, the predefined SEARCH action group grants roles permissions to use _search and _msearchAPI. |
Role |
A role is a combination of permissions and action groups, including operation permissions on clusters, indexes, documents, or fields. |
Backend role |
(Optional) Other external roles from the backend such as LDAP/Active Directory |
User |
A user can send operation requests to Elasticsearch clusters. The user has credentials such as username and password, and zero or multiple backend roles and custom attributes. |
Role mapping |
A user will be assigned a role after successful authentication. Role mapping is to map a role to a user (or a backend role). For example, the mapping from kibana_user (role) to jdoe (user) means that John Doe obtains all permissions of kibana_user after being authenticated by kibana_user. Similarly, the mapping from all_access (role) to admin (backend role) means that any user with the backend role admin (from the LDAP/Active Directory server) has all the permissions of role all_access after being authenticated. You can map each role to multiple users or backend roles. |
You can customize the username, role name, and tenant name in the OpenSearch Dashboards.
After the setting is complete, you can view the created role on the Roles page.