You should not do this. It's a common mistake that new users make, but this is not the correct user for logging into Kibana.
The kibana user is designed as a user that the Kibana application can use for its own purposes when it connects to Elasticsearch. Typically this is the user that you enter into your
For example, it is how Kibana can tell whether your ES server is available, and whether it has security turned on. You should not log in to Kibana as that user, because it doesn't have permission to do very much (which is intentional - it has just enough access to run Kibana but no more)
You should initially login to Kibana using the
elastic user. This is a superuser that can do everything.
You can use that user for everything you want to do, and always login to Kibana as elastic, but we don't recommend it. Because that user can do everything, it can make a horrible mess of your cluster if you're not careful, and one of the benefits of X-Pack security is that it can protect you from mistakes like that.
Rather, we recommend that you use the
elastic user to login the first time, and then use the Kibana admin screens to create new, lower privileged users and roles that have just the permissions that you need, but nothing more. You can then safely use those users to do your work in Kibana, and you can always login as
elastic if you need to make major changes.