# Authenticating with built-in users
**URL:** https://discuss.elastic.co/t/authenticating-with-built-in-users/321246
**Category:** Elasticsearch
**Tags:** elastic-stack-security
**Created:** [December 15, 2022, 2:35am UTC](https://discuss.elastic.co/t/authenticating-with-built-in-users/321246 "2022-12-15T02:35:07Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@zirota](https://discuss.elastic.co/u/zirota)
#### Post date: [December 15, 2022, 2:35am UTC](https://discuss.elastic.co/t/authenticating-with-built-in-users/321246/1 "2022-12-15T02:35:07Z")
Hello, I ran into some problems with authenticating with built-in users (in this case `elastic`) on my cluster nodes other than the master.
I have a cluster setup on **8.5.3** :
- 3 master nodes
- 4 data nodes
- 2 coordinator nodes
I have done:
1. First time interactive password setup for built in users
2. Added `xpack.security.authc.realms.native.native1.order: 0` in config
**Other than the master, none of the other nodes are able to authenticate the `elastic` user.**
The log shows that:
`Authentication of [elastic] was terminated by realm [reserved] was terminated by realm [reserved] - failed to authenticate user [elastic]`
This is tested via simple http requests to `https://:9200` with the `elastic` user credentials.
Is this behavior intended?
* * *
I have also tested that the nodes are able to authenticate these other types of users with no issues:
1. Native users - created via `/\_security/name/
2. AD users (after adding license)
---
### Author:  [@Yang\_Wang](https://discuss.elastic.co/u/Yang_Wang)
#### Post date: [December 15, 2022, 4:30am UTC](https://discuss.elastic.co/t/authenticating-with-built-in-users/321246/2 "2022-12-15T04:30:29Z")
No it's not the intended behaviour especially if you have done "First time interactive password setup for built in users".
What version are you using? If it is 8.0+, you can reset `elastic`'s password with the [elasticsearch-reset-password](https://www.elastic.co/guide/en/elasticsearch/reference/current/reset-password.html) CLI.
---
### Author:  [@zirota](https://discuss.elastic.co/u/zirota)
#### Post date: [December 15, 2022, 4:55am UTC](https://discuss.elastic.co/t/authenticating-with-built-in-users/321246/3 "2022-12-15T04:55:08Z")
Very thankful for the suggestion, which helped to resolve the issue. I am running v8.5.3.
In my case, I created a new superuser account via api.
Then sign in to Kibana using said user and performed a password reset for all built-in users.
Tested and verified that built-in users is able to authenticate correctly from other nodes.
Any idea what might be the root cause?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 12, 2023, 4:55am UTC](https://discuss.elastic.co/t/authenticating-with-built-in-users/321246/4 "2023-01-12T04:55:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.