lmenezes / cerebro

MIT License
5.54k stars 716 forks source link

version 0.7.2 with readonlyrest #325

Open sdba2 opened 6 years ago

sdba2 commented 6 years ago

hi,

my es is 6.1.1 and i'm working with cerebro 0.7.3 and readonlyrest 1.16.27 (just upgrade to this version).

after entering the url at the "node name" field i expected to see a login window(user+password) but didn't get one.

instead i get "unexpected response status: [403]".

at the elastic log i can see message that the readonlyrest :

[2018-10-17T12:10:24,483][INFO ][t.b.r.a.ACL ] FORBIDDEN by default req={ ID:453506563-531477318#272, TYP:ClusterHealthRequest, CGR:N/A, USR:[no basic auth header], BRS:true, KDX:null, ACT:cluster:monitor/health, OA:127.0.0.1, DA:127.0.0.1, IDX:, MET:GET, PTH:/_cluster/health, CNT:<N/A>, HDR:{User-Agent=AHC/2.0, content-length=0, Host=localhost:9205, Accept-Encoding=gzip,deflate, Accept=/}, HIS:[::Kibana::->[auth_key->false]], [::RO::->[auth_key->false]], [::RW::->[auth_key->false]], [::ADMIN::->[auth_key->false]], [::WEBSITE SEARCH BOX::->[indices->false]], [::ind1::->[groups->false]], [::ind2::->[groups->false]], [::ALL::->[groups->false]] }

1

in my real env all my users login to elastic/ror using ldap authentication.

how can i fix the problem?

ld57 commented 5 years ago

hi,

you should check on RoR forum to get an answer, but I can tell you that you won t be able to let user to logon to cerebro using ldap , and single sign on to RoR.

that I recommend to you, is to let cerebro to your super admin, and use unique encoded credentials in application.conf.

Until Lemenes works on ldap credential translation to Elasticsearch