Version: 6.x-23
Enterprise

Readonly and hidden resources

Readonly resources

You can mark any user, role, action group or roles mapping as readonly in their respective configuration files. Resources that have this flag set to true can not be changed via the REST API and are marked as reserved in the Kibana Configuration GUI.

You can use this feature to give users or customers permission to add and edit their own users and roles, while making sure your own built-in resources are left untouched. For example, it makes sense to mark the Kibana server user as readonly.

To mark a resource readonly, add the following flag:

sg_kibana_user:
  readonly: true
  ...

To add or remove the readonly flag, you need to use sgadmin.

Hidden resources

You can mark any user, role, action group or roles mapping as hidden. Resources that have this flag set to true are not returned by the REST API, and cannot be changed or deleted.

You can use this feature to give users or customers permission to add and edit their own users and roles, while making sure your own built-in resources are completely hidden.

To mark a resource hidden, add the following flag:

sg_kibana_user:
  hidden: true
  ...

Hidden resources are read-only by definition.

To add or remove the readonly flag, you need to use sgadmin.


Not what you were looking for? Try the search.