Anonymous acces for Kibana through X-Pack

Hello :slight_smile:

I've changed my config according to https://www.elastic.co/guide/en/x-pack/current/anonymous-access.html (plus kibana_user role) and the user appeared in Kibana user management, but I don't know how I can access Kibana anonymously now. Accessing ES through REST is working anonymously.
Is there any way to get it working with Kibana?

Thanks
Grevius

If you don't want the login screen to show up for anyone using Kibana, you can disable security in kibana.yml: xpack.security.enabled: false

This should work so that all users accessing Kibana will default to the anonymous user you set up.

Thanks for your answer. Apparently Kibana doesn't start if I set this option. Here's the log:

Aug 09 22:47:47 hostname systemd[1]: Started Kibana.
Aug 09 22:47:53 hostname kibana[30429]: {"type":"log","@timestamp":"2017-08-09T20:47:53Z","tags":["fatal"],"pid":30429,"level":"fatal","message":"EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/graph.entry.js'","error":{"message":"EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/graph.entry.js'","name":"Error","stack":"Error: EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/graph.entry.js'\n    at Error (native)","code":"EACCES"}}
Aug 09 22:47:53 hostname kibana[30429]: FATAL { Error: EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/graph.entry.js'
Aug 09 22:47:53 hostname kibana[30429]:     at Error (native)
Aug 09 22:47:53 hostname kibana[30429]:   cause:
Aug 09 22:47:53 hostname kibana[30429]:    { Error: EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/graph.entry.js'
Aug 09 22:47:53 hostname kibana[30429]:        at Error (native)
Aug 09 22:47:53 hostname kibana[30429]:      errno: -13,
Aug 09 22:47:53 hostname kibana[30429]:      code: 'EACCES',
Aug 09 22:47:53 hostname kibana[30429]:      syscall: 'open',
Aug 09 22:47:53 hostname kibana[30429]:      path: '/usr/share/kibana/optimize/bundles/graph.entry.js' },
Aug 09 22:47:53 hostname kibana[30429]:   isOperational: true,
Aug 09 22:47:53 hostname kibana[30429]:   errno: -13,
Aug 09 22:47:53 hostname kibana[30429]:   code: 'EACCES',
Aug 09 22:47:53 hostname kibana[30429]:   syscall: 'open',
Aug 09 22:47:53 hostname kibana[30429]:   path: '/usr/share/kibana/optimize/bundles/graph.entry.js' }
Aug 09 22:47:53 hostname systemd[1]: kibana.service: Main process exited, code=exited, status=1/FAILURE
Aug 09 22:47:53 hostname systemd[1]: kibana.service: Unit entered failed state.
Aug 09 22:47:53 hostname systemd[1]: kibana.service: Failed with result 'exit-code'.
Aug 09 22:47:53 hostname systemd[1]: kibana.service: Service hold-off time over, scheduling restart.
Aug 09 22:47:53 hostname systemd[1]: Stopped Kibana.

When I revert the change Kibana starts fine... :face_with_raised_eyebrow:

EDIT:
It turns out that this is a current bug: https://github.com/elastic/kibana/issues/8818

I've took this workaround and now I have the following problem:

Which roles or permissions does the anonymous user need? And it seems that it is now impossible to login into any other account. Is that the case?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.