opensearch-project / opensearch-project/data-prepper
Feature request - add SSL mutual authentication and metadata to http input
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 374
- Forks
- 354
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem? Please describe.
Not related to a problem - this is a feature request
Describe the solution you'd like
SSL mutual authentication should be added to the http input for securing communications from clients.
Additionally - it would be optimal to provide metadata to the pipeline for information about the client.
For example, logstash provide the following when using 'beats' input:
host
ip_address
tls_peer.status
tls_peer.protocol
tls_peer.subject
tls_peer.cipher_suite
Describe alternatives you've considered (Optional)
N/A.
Additional context
Please see the 'ssl_verify_mode' and metadata references in the articles below
https://www.elastic.co/guide/en/beats/filebeat/current/configuring-ssl-logstash.html
https://www.elastic.co/guide/en/logstash/current/plugins-inputs-beats.html
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the http input entry point and reviewing its existing SSL configuration. Compare the requested mutual authentication and client metadata with the linked Filebeat and Logstash references. Done means clients can be authenticated mutually and the requested client and TLS details are available to the pipeline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100