Add Kerberos-aware Elasticsearch and integration test to ES output #18127
Conversation
This file contains 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
kvch
added
needs_backport
|
Pinging @elastic/integrations-services (Team:Services) |
botelastic
bot
added
the
needs_team
ycombinator
reviewed
Apr 30, 2020
ycombinator
reviewed
Apr 30, 2020
ycombinator
approved these changes
Apr 30, 2020
ycombinator
removed
the
needs_team
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
kvch
force-pushed
the
testing-libbeat-kerberos
branch
from
78f336e to
c4b90e3
Compare
kvch
added a commit
to kvch/beats
that referenced
this pull request
May 4, 2020
…lastic#18127) This PR adds an integration test to the Elasticsearch output to check Kerberos authentication. Furthermore, it adds a new element to our testing environment, a Kerberos-aware Elasticsearch instance named `elasticsearch_kerberos.elastic`. (cherry picked from commit 428ee72)
kvch
added
v7.8.0
and removed
needs_backport
kvch
added a commit
that referenced
this pull request
May 4, 2020
…ration test to ES output (#18168) * Add Kerberos-aware Elasticsearch and integration test to ES output (#18127) This PR adds an integration test to the Elasticsearch output to check Kerberos authentication. Furthermore, it adds a new element to our testing environment, a Kerberos-aware Elasticsearch instance named `elasticsearch_kerberos.elastic`. (cherry picked from commit 428ee72) * downgrade dockerfile version to 7.7
|
I think some AD environment would still be needed. I don't know if we would be able to use for automated testing but just for support scenarios I think it would be very useful. What options do we have here? |
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.
What does this PR do?
This PR adds an integration test to the Elasticsearch output to check Kerberos authentication.
Furthermore, it adds a new element to our testing environment, a Kerberos-aware Elasticsearch instance named
elasticsearch_kerberos.elastic.Why is it important?
To make sure Kerberos authentication is working.
Checklist
- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.