[ADDED] LeafNode: TLSHandshakeFirst option #4119
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A new field in
tls{}
blocks force the server to do TLS handshake before sending the INFO protocol.Note that if
handshake_first
is set in the "accept" side, the firsttls{}
block in the example above, a server trying to create a LeafNode connection to this server would need to havehandshake_first
set to true inside thetls{}
block of the corresponding remote.Configuration reload of leafnodes is generally not supported, but TLS certificates can be reloaded and the support for this new field was also added.
Signed-off-by: Ivan Kozlovic ivan@synadia.com