GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing www.elastic.co — Setting Up User Authentication | X-Pack for the Elastic Stack [6.2] | Elastic WARNING: Version 6.2 of the Elastic Stack has passed its EOL date. This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation. Setting Up User Authenticationedit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.
Setting Up User AuthenticationeditAuthentication identifies an individual. To gain access to restricted resources, a user must prove their identity, via passwords, credentials, or some other means (typically referred to as authentication tokens). You can use the native support for managing and authenticating users, or integrate with external user management systems such as LDAP and Active Directory. For information about managing native users, see Managing Native Users. Built-in UserseditX-Pack security provides built-in user credentials to help you get up and running.
These users have a fixed set of privileges and cannot be authenticated until their
passwords have been set. The
How the Built-in Users WorkeditThese built-in users are stored within a special Although they share the same API, the built-in users are separate and distinct from users managed by the native realm. Disabling the native realm will not have any effect on the built-in users. The built-in users can be disabled individually, using the user management API. The Elastic Bootstrap PasswordeditWhen you install X-Pack, if the By default, the bootstrap password is derived from a randomized After you set passwords for the built-in users,
in particular for the Setting Built-in User PasswordseditYou must set the passwords for all built-in users. The bin/x-pack/setup-passwords interactive For more information about the command options, see setup-passwords. After you set a password for the Alternatively, you can set the initial passwords for the built-in users by using
the Management > Users page in Kibana or the
Change Password API. These methods are
more complex. You must supply the bin/elasticsearch-keystore add "bootstrap.password" You can then start Elasticsearch and Kibana and use the Adding Built-in User Passwords To Kibana and LogstasheditAfter the elasticsearch.password: kibanapassword The To enable this feature in Logstash, you need to update the Logstash
configuration with the new password by setting xpack.monitoring.elasticsearch.password: logstashpassword If you have upgraded from an older version of elasticsearch/x-pack,
the PUT _xpack/security/user/logstash_system/_enable Disabling Default Password FunctionalityeditThis setting is deprecated. The elastic user no longer has a default password. The password must be set before the user can be used. See The Elastic Bootstrap Password. Internal UserseditX-Pack security has three internal users ( These users are only used by requests that originate from within the cluster. For this reason, they cannot be used to authenticate against the API and there is no password to manage or reset. From time-to-time you may find a reference to one of these users inside your logs, including audit logs. |
| You are visitor 01402605 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |