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 ability to configure client TLS enabled protocol versions and cipher suites via Spring properties #640

Conversation

mryangza
Copy link
Contributor

@mryangza mryangza commented Mar 15, 2021

  • Adding the ability to explicitly configure the enabled SSL protocol
    versions and cipher suites used by the Vault HTTP client via the
    following Spring properties:

    • vault.ssl.enabled-protocols
    • vault.ssl.enabled-cipher-suites
  • Properties should be a comma-separated list of String constants that
    correspond to those used by the enabled SSL provider.

Closes gh-635

suites via Spring properties

- Adding the ability to explicitly configure the enabled SSL protocol
versions and cipher suites used by the Vault HTTP client via the
following Spring properties:

* vault.ssl.enabled-protocols
* vault.ssl.enabled-cipher-suites

- Properties should be a comma-separated list of String constants that
correspond to those used by the enabled SSL provider.

Closes spring-projectsgh-635
@mryangza mryangza changed the title Add ability to configure client TLS enabled protocol versions and cipher Add ability to configure client TLS enabled protocol versions and cipher suites via Spring properties Mar 15, 2021
@mp911de mp911de added the type: enhancement A general enhancement label Mar 16, 2021
@mp911de mp911de added this to the 2.3.2 milestone Mar 16, 2021
mp911de pushed a commit that referenced this pull request Mar 16, 2021
…her suites via Spring properties.

- Adding the ability to explicitly configure the enabled SSL protocol
versions and cipher suites used by the Vault HTTP client via the
following Spring properties:

* vault.ssl.enabled-protocols
* vault.ssl.enabled-cipher-suites

- Properties should be a comma-separated list of String constants that
correspond to those used by the enabled SSL provider.

Closes gh-635
Original pull request: gh-640.
mp911de added a commit that referenced this pull request Mar 16, 2021
Make SslConfiguration.enabledProtocols and enabledCipherSuites non-null. Update since tags. Add author tags. Update documentation.

See gh-635
Original pull request: gh-640.
mp911de pushed a commit that referenced this pull request Mar 16, 2021
…her suites via Spring properties.

- Adding the ability to explicitly configure the enabled SSL protocol
versions and cipher suites used by the Vault HTTP client via the
following Spring properties:

* vault.ssl.enabled-protocols
* vault.ssl.enabled-cipher-suites

- Properties should be a comma-separated list of String constants that
correspond to those used by the enabled SSL provider.

Closes gh-635
Original pull request: gh-640.
mp911de added a commit that referenced this pull request Mar 16, 2021
Make SslConfiguration.enabledProtocols and enabledCipherSuites non-null. Update since tags. Add author tags. Update documentation.

See gh-635
Original pull request: gh-640.
@mp911de
Copy link
Member

mp911de commented Mar 16, 2021

Thank you for your contribution. That's merged, polished, and backported now.

@mp911de mp911de closed this Mar 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement A general enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add ability to configure client TLS enabled protocol versions and cipher suites via Spring properties
2 participants