When the login request from Kibana plugin matches into an ACL block that has no authentication rule (auth_key*, ldap_auth*, etc), then you are returned with an identity object that does not have a username. A username is necessary for kibana session to begin.
Please go back to your ACL and your elasticsearch logs (grep for “metadata”) and see what ACL block has matched the login attempt.
These elastic node and kibana are deploy on a Kubernetes environement, so I am lost to where to find these elasticsearch log that You are talking about
the elasticsearch HOME DIRECTORY is /usr/share/elasticsearch/
and I only have 2 logs file under /usr/share/elasticsearch/logs
which are gc.log and gc.log.00
none of them containt the key word “metadata”
The logs line that I mentioned in the question come from the kibana pods logs
Is there another way around to find what is causinig the issue, given this set uo
I am available to provide more information if needed
you could change the ACL and enable “audit_log_collector: true”, so you will have those logs in readonlyrest-audit-* indices, and you can see them directly in Kibana, or query directly from Elasticsearch I suppose!