-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Kerberos Authentication for Elasticsearch #7404
Comments
It does look like the https://github.com/jcmturner/gokrb5 library should support what we need to integrated with ES:
For testing purposes we can setup dockerized kerberos environment. Here's a RedHat guide: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system-level_authentication_guide/configuring_a_kerberos_5_server I've been told another good resource for getting started is https://github.com/freeipa/freeipa-workshop. |
The ES team has a test fixture for Kerberos at https://github.com/elastic/elasticsearch/tree/master/test/fixtures/krb5kdc-fixture. In Kerberos auth feature in ES is being worked from a feature branch at: https://github.com/elastic/elasticsearch/commits/feature/kerberos |
The mering and backporting of the automated tests: #18127 |
I've merged and backported the automated tests. |
Hi @kvch I encounterd the same problem mentioned here: #IBM/sarama#1658, did you find a workaroud? |
@ovictorain Thanks for reporting it. Do you mind opening a separate issue, so we can track it? The fix is not yet integrated into Beats. I agree it is not elegant. My plan is to open a PR with the revert. But until it gets merged upstream, we have no choice but to use a fork of the repository. :) I rather not keep our users waiting. :) |
@ovictorain Now I am looking at the issue you commented on. Kerberos authentication for Elasticserach has nothing to do with Kafka. What output are you using? What is the error you are getting? |
Elasticsearch (by way of X-Pack) is adding support for authenticating via Kerberos. As a Beats user I'd like to be able to use Kerberos for authenticating with the Elasticsearch output cluster (or monitoring cluster).
There is a pure Go client that is Apache 2.0 licensed -- https://github.com/jcmturner/gokrb5. We should test this to see if it meets our requirements. If not there are a few other libraries (mostly that require cgo).
Based on the ES ticket it sounds like the flow will be to authenticate to ES with the Kerberos ticket and exchange it for an Elasticsearch token. Then use the ES token when making the _bulk requests.
Related Tickets
The text was updated successfully, but these errors were encountered: