In short, the steps explained by Stephen in Anonymous Kibana Users - #9 by stephenb is what you need to cover this use case. Only changes in Kibana configuration are needed, no need to modify Elasticsearch config. Don't be be confused by the Login Selector part, if you use
iframe code for the dashboard to embed into your Sharepoint page as explained here, your users won't see login selector, iframe will load required dashboards directly.
I'd encourage you to go through all the links we've shared in this thread to get a better understanding of how anonymous access is configured exactly. You seem to be confused by the fact that there are two distinct features Elasticsearch anonymous access and Kibana anonymous access. You may want to use Elasticsearch anonymous access if, for example, you want to query Elasticsearch directly (without Kibana) without providing any sort of credentials. It's enabled by default in Cloud (you cannot change that), but it's required that you create an
anonymous role to make it work first. If I understand your use case correctly you don't need this at all, so I won't go into details here.
As explained in the links above, Kibana anonymous access can leverage Elasticsearch anonymous access internally (
credentials - "elasticsearch_anonymous_user" ), but it's not required. The easiest way is to just a create a user that will be used as anonymous service account and use username/password
credentials as Stephen has already suggested.
Irrespective to the type of credentials you use, when you embed Kibana dashboards or visualizations with toggled
Public URL switch, Login Selector won't be shown to your users as this switch tells Kibana to use anonymous access if it's enabled.
Let me know if there is anything that's still unclear, happy to clarify.