Allow bidirectional communication with AutoTLS enabled #179
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t auto mTLS in bidirectional communication.
|
|
|
Thanks for the contribution! There was a bit more required to make the mTLS connection. This was fixed in #193 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently enabling AutoTLS when connecting from a plugin back to host ends with
transport: authentication handshake failed: x509: certificate is valid for localhost, not unusedas described in #109.This PR sets ServerName and RootCAs in
tls.Configon the server-side with the certificate received from the host. This allows to successfully establish the connection.Fixes #109