-
Notifications
You must be signed in to change notification settings - Fork 988
Support SPNEGO/Kerberos auth to Elasticsearch #1175
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
Comments
@jbaiera |
There is a substantial amount of work that is already completed for this feature, but there is quite a bit more to go, including the extensive testing that we will need to eventually run to ensure correctness. Additionally, we are working out the best course of action for handling token authentication in worker tasks. The current token functionality in ES is based on OAuth username and password grants, which does not provide tokens that are useable in Hadoop/Spark/Storm (the tokens change between refreshes, last only an hour, can only be refreshed once, etc). Hopefully soon I will be able to pull together a preliminary PR for the work, but until then, I have the work periodically checked into a feature branch located at master...jbaiera:feature-kerberos |
This is currently waiting on #1183 |
We already had parsing code for this dating back to the 2.x era. Lucky us. fixes #1175
Closed in error. |
This is currently waiting on elastic/elasticsearch#34383 for further development |
#1244 is merged now. |
Work is wrapping up on adding a Kerberos based authentication realm to Elasticsearch. The realm will secure the rest endpoints by means of SPNEGO. Since Kerberos is used heavily in the Big Data space, we should offer an integration that allows for ES-Hadoop to use the currently logged in user and their Kerberos Ticket to authenticate to Elasticsearch over SPNEGO. This should include token authentication and appropriate refreshing mechanisms to avoid the same pitfalls that Hadoop runs into with KDC spamming and token lifetime.
The text was updated successfully, but these errors were encountered: