The recommended approach for enabling Kibana access is to grant the user the kibana_user role.
Is there a reason that you want to incorporate those permissions into each of your own roles (such as GeneralUser) instead of just including kibana_user in the user's role list?
It's technically possible to do what you want (via the API) but it's not the intended approach.
Thank you for the reply. Yes I followed your link and I was able to search index with newly created user with kibana_user role.
However, I have a requirement where multiple roles per company department is required and need to assign each employee to the role. Which will end up having different Indice privilege among the roles.
Thus, to achieve this , instead of setting indice privilege of .kibana to GeneralUser, I have just tried assigning kibana_user as Run As Privilege but I get search denied error in the audit log. As a result, nothing was returned in discovery.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.