You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
secure -> ssl_enabled
ca_file -> ssl_certificate_authorities
Add common settings validations
Not allow mixing the same deprecated and new setting on the same plugin configuration, e.g. secure and ssl_enabled
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_certificate
ssl_certificate_authorities
ssl_cipher_suites
ssl_handshake_timeout
ssl_key
ssl_key_passphrase
ssl_supported_protocols
ssl_verification_mode
ssl_keystore_path
ssl_keystore_password
ssl_keystore_type
ssl_keystore_key_password
ssl_truststore_path
ssl_truststore_password
ssl_truststore_type
The text was updated successfully, but these errors were encountered:
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
Add common settings validations
secure
andssl_enabled
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)
The text was updated successfully, but these errors were encountered: