[FAB-18298] Default cluster cert and key #2078
Merged
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
wlahti
reviewed
Nov 5, 2020
Signed-off-by: Tiffany Harris <tiffany.harris@ibm.com> Signed-off-by: Will Lahti <wtlahti@us.ibm.com>
lindluni
approved these changes
Nov 6, 2020
|
@pamandrejko @joealewine @stephyee This should probably require a doc update (and should simplify our tutorials since it's a couple parameters that don't need to be specified). |
|
@jyellick Pam did note that in the JIRA. Should we also backport to 2.2? |
|
@Mergifyio backport release-2.2 |
|
Command
|
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.
Type of change
Description
When cluster listener is reused, default cluster client certificate and private key (if not set) to the TLS server certificate and key.
Related issues
FAB-18298