-
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
[http_endpoint] fix incorrect TLSConfig initialization (#32104) #32105
[http_endpoint] fix incorrect TLSConfig initialization (#32104) #32105
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
This pull request is now in conflicts. Could you fix it? 🙏
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume you tested without TLS client authentication. Could you verify client auth (mTLS) is working too.
It looks to me like mTLS should not work with the code that is currently in main; this should fix that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but please wait for @andrewkroh
I'm very suspicious of the code in the
Hopefully I'm wrong about some of this. I think the tlscommon package needs some unit tests. |
For
with |
I might have misunderstood. But isn't this what you're looking for -
I will look a little further into the hostname check and verify strict. |
The piece I was missing was that there is a |
* [http_endpoint] fix incorrect TLSConfig initialization * update Changelog (cherry picked from commit 1a75aea)
* [http_endpoint] fix incorrect TLSConfig initialization * update Changelog (cherry picked from commit 1a75aea)
* [http_endpoint] fix incorrect TLSConfig initialization * update Changelog
What does this PR do?
The PR fixes #32104.
Why is it important?
Without this fix
http_endpoint
cannot receive events due to TLS handshake errors.Checklist
[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
Logs
Shows logs indicating events being received and then sent to ES