This documentation remains in a beta state. It has content gaps and might contain bugs.
After you configure the security plugin to use your own certificates and preferred authentication backend, you can start adding users, creating roles, and mapping roles to users.
This section of the documentation covers what a user is allowed to see and do after successfully authenticating.
|Permission||An individual action, such as creating an index (e.g. |
|Action group||A set of permissions. For example, the predefined |
|Role||Security roles define the scope of a permission or action group: cluster, index, document, or field. For example, a role named |
|Backend role||(Optional) Arbitrary strings that you specify or that come from an external authentication system (e.g. LDAP/Active Directory). Backend roles can help simplify the role mapping process. Rather than mapping a role to 100 individual users, you can map the role to a single backend role that all 100 users share.|
|User||Users make requests to OpenSearch clusters. A user has credentials (e.g. a username and password), zero or more backend roles, and zero or more custom attributes.|
|Role mapping||Users assume roles after they successfully authenticate. Role mappings, well, map roles to users (or backend roles). For example, a mapping of |
The security plugin comes with a number of predefined action groups, roles, mappings, and users. These entities serve as sensible defaults and are good examples of how to use the plugin.