# ECK: User created by FileRealm not show in 'GET \_security/user'

**URL:** <https://discuss.elastic.co/t/eck-user-created-by-filerealm-not-show-in-get-security-user/371432>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Tags:** elastic-stack-security\
**Created:** [December 4, 2024, 4:36am UTC](https://discuss.elastic.co/t/eck-user-created-by-filerealm-not-show-in-get-security-user/371432 "2024-12-04T04:36:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![thuanpham582002](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thuanpham582002/32/139574_2.png) [@thuanpham582002](https://discuss.elastic.co/u/thuanpham582002)\
**Post date:** [December 4, 2024, 4:36am UTC](https://discuss.elastic.co/t/eck-user-created-by-filerealm-not-show-in-get-security-user/371432/1 "2024-12-04T04:36:35Z")

</div>

I don't understand why no user returns from GET \_security/user.  
This is my eck config. (I deploy eck by helm).

```yaml
eck-elasticsearch:  
  enabled: true  
  # This is adjusting the full name of the elasticsearch resource so that both the eck-elasticsearch  
  # and the eck-kibana chart work together by default in the eck-stack chart.  
  fullnameOverride: elasticsearch  
  filebeat:  
    auth:  
      username: filebeat  
      password: Anhyeuem2002a@  
      roles: 'superuser,filebeat,kibana_admin,ingest_admin'  
  auth:  
    fileRealm:  
      - secretName: filebeat-basic-auth  
    roles:  
      - secretName: filebeat-roles  

```

I am sure that I can login with the account filebeat in kibana. Thank you!

---

<div class="post-metadata">

**Author:** ![thuanpham582002](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thuanpham582002/32/139574_2.png) [@thuanpham582002](https://discuss.elastic.co/u/thuanpham582002)\
**Post date:** [December 4, 2024, 6:56am UTC](https://discuss.elastic.co/t/eck-user-created-by-filerealm-not-show-in-get-security-user/371432/4 "2024-12-04T06:56:00Z")

</div>

`As the administrator of the cluster, it is your responsibility to ensure the same users are defined on every node in the cluster. The Elastic Stack security features do not deliver any mechanism to guarantee this. You should also be aware that you cannot add or manage users in the `file` realm via the [user APIs](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api.html#security-user-apis) and you cannot add or manage them in Kibana on the **Management / Security / Users** page`I found this. Maybe help those who come after.