Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For ML setup, Kibana credentials are not inherited from the Elasticsearch output #6992

Closed
tsg opened this issue May 2, 2018 · 3 comments
Closed

Comments

@tsg
Copy link
Contributor

tsg commented May 2, 2018

  • Version: 6.3
  • Steps to Reproduce:
  • Install ES and KB with security enabled.
  • Configure the Elasticsearch output with username: elastic and password: changeme.
  • Try ./filebeat setup -e --machine-learning

You get an error because Kibana doesn't have the credentials. I was expecting the Kibana connection to inherit the credentials from the ES output, and that works fine for the dashboards.

If you add setup.kibana.username: elastic and setup.kibana.password: changeme, loading ML configs works again.

@ruflin
Copy link
Contributor

ruflin commented May 3, 2018

@tsg As #6993 is merged, can this one be closed?

@tsg
Copy link
Contributor Author

tsg commented May 3, 2018

Yes, I linked the wrong issue in the commit. Thanks!

@tsg tsg closed this as completed May 3, 2018
@LeeDr
Copy link

LeeDr commented May 7, 2018

I don't think inheriting the credentials makes sense. We shouldn't assume everyone is using the super user everywhere in their stack.
In my testing, I create a user who has write access to *beats* index patterns and use that in the output.elasticsearch section. And I use the kibana server user in the setup.kibana section (and even that is using more privileges than needed). The setup.kibana section should probably use a user who only has the kibana_user role.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants