Kibana not starting for enabling AD security

[ikakavas (Ioannis Kakavas)]

@bharat1

I noticed I was able to login via elastic user but not with kibana user (gave me error - "{"statusCode":403,"error":"Forbidden","message":"Forbidden"}" )

kibana user is meant to be used for kibana to communicate to elasticsearch and not to be used by end users. This is expected behavior and it works as it's designed to work, no need to worry.

@bharat1

I used elasticsearch.username as kibana and in configuration I have used below, does this mean though kibana user is mentioned it will not be allowed to login in first instance rather to do some backend work and do more to give privileges to login as kibana user?

No, it doesn't mean that. it will work fine, no need to worry.

@bharat1

A question, since we have this cluster integrated with AD, for all users in AD to give them access to various dashboards, do I need to create all those AD users here in Kibana? I assume not so because it may be tedious job to create huge number of users here in Kibana. Then what is the way out?

I replied to this in Kibana not starting for enabling AD security - #10 by ikakavas

@ikakavas

You would need to give the users the necessary roles .read through Granting access to Kibana | Kibana Guide [8.11] | Elastic. when you have the roles ready, you can assign the roles to users in your roles.yml file that you already have

Please read through the docs.