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

Logstash - Plugins - SSL Settings Standardization - Standardize JMS INPUT settings #14936

Open
Tracked by #14905
edmocosta opened this issue Feb 28, 2023 · 0 comments
Open
Tracked by #14905

Comments

@edmocosta
Copy link
Contributor

edmocosta commented Feb 28, 2023

This issue should make the plugin SSL settings consistent with the naming convention defined in the meta issue. Missing settings already supported by the plugin's HTTP/TCP client, which only requires small coding changes on the plugin source, should also be added through this issue.

Add and deprecate options to comply with the naming convention

  • keystore -> ssl_keystore_path
  • keystore_password -> ssl_keystore_password
  • truststore -> ssl_truststore_path
  • truststore_password -> ssl_truststore_password

Add common settings validations

  • Not allow mixing the same deprecated and new setting on the same plugin configuration, e.g. keystore and ssl_keystore_path

Add missing settings/functionality that fits into the phase 1 description, and move non-phase 1-2 to the phase 3 issue (to be created if doesn't exist)

  • ssl_enabled
  • ssl_certificate
  • ssl_certificate_authorities
  • ssl_cipher_suites
  • ssl_handshake_timeout
  • ssl_key
  • ssl_key_passphrase
  • ssl_supported_protocols
  • ssl_verification_mode
  • ssl_keystore_type
  • ssl_keystore_key_password
  • ssl_truststore_type
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant