Hello everyone, It seems that if I created users/roles/tenants over the API and run secureadmin.sh afterwards for whatever reason to update the cluster security configuration, it will delete any previous record added over the API. Is this the expected behavior ? I find this problematic. Thanks!

have you found solution for this?

I answered a similar question in another thread about this. [image] Users gone after using securityadmin.sh Security So i will lose configuration from kibana when i use securityadmin.sh? No, if you only load the config.yml instead of the entire /securityconfig/ dir you …

Thanks ejohns81 I understood this but my problem is, I am automating everything in chef so that i can manage and changes internal user(admin,kibanaserver,logstash etc) password anytime for different env. I am maintaining password in vault and reading it from there new password (if i change) and up…

Hi, We ended up doing everything over the OD API for users. When we create the cluster we have ofcourse the initial users (admin,management and 1 for monitoring). From that point on we do everything over REST and no need to call the securityadmin.sh anymore. We simply did some automation to call t…

Thanks Valentin for quick response. But what if you want to change the password for internal users like admin etc?

You do it over the API or Kibana. br

We can not change admin and kibanaserver password from kibana UI, all other user we can manage from kibana, thats a problem :frowning: [image] Change your Admin Passwords in Open Distro for Elasticsearch | Amazon Web... 中文版 – Open Distro for Elasticsearch ships with an advanced securit…

This is exactly what i want to do but it looks like the API wipes out my entire configuration. I want to use the API to update the password of our bind id. Before doing it, i wanted to do a simple update, for example: PATCH {curhost}/_opendistro/_security/api/securityconfig [ { “op”: “replace”…

I don’t do these kind of updates via the API yet, it my case it’s just users (CRUD). I suspect you hit a bug and it’s not transparent on whats happening into the backend.

I have a similar problem. I configured a cluster with terraform using securityadmin.sh as a final step. Everithing ok, but if I add/edit some role all my previous configuration dissapear forcing me to run securityadmin.sh again to recover my config. For testing roles pruposes I prefer to use the ki…

Running securityadmin.sh deletes the roles/tenants created over the API

Security

ejohns81 February 24, 2020, 10:07pm 3

I answered a similar question in another thread about this.

Topic		Replies	Views
Users gone after using securityadmin.sh Security	4	3134	February 22, 2021
Security entries lost after modifiying admin password Security	2	1122	May 13, 2019
Securityadmin.sh fails to update cluster config when using kirk certificates Security	3	6156	October 17, 2019
Best option for automating role creation in Kibana? Security	9	1084	September 14, 2020
Roles created through securityadmin.sh get deleted when using the API to create Roles Security troubleshoot , configure	20	938	October 18, 2022

Running securityadmin.sh deletes the roles/tenants created over the API

Related topics