Skip to content
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

Add ssl_peer_metadata option analogous to input-beats #166

Open
AydinChavez opened this issue Feb 2, 2021 · 0 comments
Open

Add ssl_peer_metadata option analogous to input-beats #166

AydinChavez opened this issue Feb 2, 2021 · 0 comments

Comments

@AydinChavez
Copy link

The logstash input plugin for beats supports the ssl_peer_metadata option, which allows logstash to extract the DN fields of client certificates:
https://www.elastic.co/guide/en/logstash/current/plugins-inputs-beats.html#plugins-inputs-beats-ssl_peer_metadata

This is a very important feature which also allows to whitelist certain clients.

The logstash input plugin for tcp however does not offer that option. Please implement it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant