You work with users and roles in the Kibana Management app, accessible from the Security page in the Elasticsearch Add-On for Heroku console or directly from the Kibana side navigation.
The Users tab shows the users that have been configured on your deployment. You can add or delete users here and assign roles that give users specific privileges. A user can be assigned multiple roles.
admin user in X-Pack">
If you upgraded your deployment to Elasticsearch 5.0 or later from a version before 5.0, the users defined in Shield were also migrated to X-Pack and show up in this list. This includes the default
readonly users, which you can work with like any other user in the Kibana Management app.
The Roles tab shows the roles that exist on your deployment. Roles let you customize exactly which actions a user with the role can do, both on a deployment and an index level. Several users can have the same role. You can also add or delete users.
admin role in X-Pack">
Two users are always created with new version 5.x deployments:
A superuser that is somewhat similar in scope to the default
adminuser in Shield configurations in Elasticsearch Add-On for Heroku before version 5.0. The
elasticuser is not shown in the Kibana Management app and you cannot modify this user, other than to reset the password.
A user for handling incoming requests where no authentication token can be extracted. By default, this user has no privileges. It is NOT recommended to provide any privileges to that user and role, and as a best practice you should NOT enable anonymous access for production environments. In Elasticsearch versions 7.10 and higher, the
anonymoususer is disabled by default. If your use case requires unauthenticated access, you can enable it by adding the
xpack.security.authc.anonymous.*setting to the
elasticsearch.ymlfile. In versions prior to 7.10, you can add the setting to prevent anonymous access being accidentally disabled by a subsequent upgrade. For details, see enabling anonymous access.
To learn more about users and roles, see User authentication.