however, when I try to access the cluster via head plugin using the user esadmin (that is defined in the esadmin-keystore.jks), I get this error in cluster log-
[2017-04-19T09:50:58,869][INFO ][c.f.s.a.BackendRegistry ] Cannot authenticate user (or add roles) with ad 4 due to ElasticsearchSecurityException[com.google.common.util.concurrent.UncheckedExecutinException: ElasticsearchSecurityException[esadmin not found]]; nested: UncheckedExecutionException[ElasticsearchSecurityException[esadmin not found]]; nested: ElasticsarchSecurityException[esadmin not found];, try next
I tried editing these files and add these settings-
Issue resolved, after reading the documentation in https://github.com/floragunncom/search-guard-docs/blob/master/sgadmin.md, I understood that changes done in sgconfig are going into effect not after elasticsearch service restart, but after running sgadmin again. after doing so, the user is recognizable by elastic.
בתאריך יום רביעי, 19 באפריל 2017 בשעה 15:07:40 UTC+3, מאת HilaF:
···
Hey,
I’ve initialized the elastic search cluster with searchguard index using sgadmin-
however, when I try to access the cluster via head plugin using the user esadmin (that is defined in the esadmin-keystore.jks), I get this error in cluster log-
[2017-04-19T09:50:58,869][INFO ][c.f.s.a.BackendRegistry ] Cannot authenticate user (or add roles) with ad 4 due to ElasticsearchSecurityException[com.google.common.util.concurrent.UncheckedExecutinException: ElasticsearchSecurityException[esadmin not found]]; nested: UncheckedExecutionException[ElasticsearchSecurityException[esadmin not found]]; nested: ElasticsarchSecurityException[esadmin not found];, try next
I tried editing these files and add these settings-