Add support for Kerberized Elasticsearch #1244
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add renewer to services meta file. Move token identifier to mr package.
Wrap the whole token instead of just the access code. Rename TokenCredentials to EsTokenCredentials. Mark auth scheme complete after first call. Subsequent calls will attempt to re-read the authentication token from the provider. TokenCredentialProvider to deserialize the token data from the hadoop token.
Move the token identifier to the security package.
We do this in case we need to swap out the user facilities for a different integration.
Add a kerberos qa subproject.
Test the SPNEGO auth end-to-end. Add configurations for specifying the user and service principals. Negotiator should use non-chunked Base64 encoding. Only set preemptive auth when basic authentication is used.
Will most likely need another pass of determining if this is the best place to do this. We don't support multiple ES cluster outputs yet, but Storm is probably the easiest place to do it. That said, our tokens don't fully support it, and thus, we will have to deal with it.
Instead we'll just grab the cluster info from the token available on the current subject when the job kicks off.
|
Closes #1175 |
jbaiera
added a commit
that referenced
this pull request
Feb 5, 2019
Elasticsearch supports using Kerberos to authenticate over HTTP by means of SPNEGO. Since most secure Hadoop environments make use of Kerberos to secure their environments, naturally ES-Hadoop should support Kerberos authentication. With the recent addition of API Key authentication to Elasticsearch, we now have a stable means for obtaining long lived and stable tokens for worker process authentication when using Kerberos.
This was referenced Oct 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Elasticsearch supports using Kerberos to authenticate over HTTP by means of SPNEGO. Since most secure Hadoop environments make use of Kerberos to secure their environments, naturally ES-Hadoop should support Kerberos authentication.
With the recent addition of API Key authentication to Elasticsearch, we now have a stable means for obtaining long lived and stable tokens for worker process authentication when using Kerberos.
This PR contains the following changes: