-
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
Remove deprecated TLS fields #28487
Remove deprecated TLS fields #28487
Conversation
* Remove tls.detailed.server_certificate and tls.detailed.client_certificate in favor of x509 fields in tls.server.x509 and tls.client.x509 respectively * Addresses part of elastic#19039
…ls.server.x509.version, tls.server.x509.subject.province
Pinging @elastic/integrations (Team:Integrations) |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
* Remove version and province fields * Remove tls.detailed.server_certificate and tls.detailed.client_certificate in favor of x509 fields in tls.server.x509 and tls.client.x509 respectively * Update fields and documentation * Update python unit tests to remove tls.detailed.server_certificate, tls.server.x509.version, tls.server.x509.subject.province * Update changelog
What does this PR do?
This PR removes deprecated fields in favor of those in
tls.server.x509
andtls.client.x509
-version
->tls.server.x509.version
,province
->tls.server.x509.subject.province
tls.detailed.server_certificate
tls.detailed.client_certificate
Why is it important?
Removes duplicate TLS fields.
Checklist
I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
Author's Checklist
How to test this PR locally
From
packetbeat
directory run -Related Issues
Use cases
Screenshots
Logs