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

Update core.yaml, orderer.yaml and docs for TLS #2141

Merged
merged 1 commit into from
Nov 17, 2020

Conversation

denyeart
Copy link
Contributor

Type of change

  • Documentation update

Description

Update TLS instructions in yaml files and docs.
Specifically, indicate that TLS CA certs and client TLS CA certs do not
need to be configured on every peer and orderer, since peers and orderers
automatically use the TLS CA certs that exist in the channel configuration.
However, additional TLS CA certs can be configured for peers and orderers to
augment the list of TLS CA certs from the channel configuration.

Signed-off-by: David Enyeart enyeart@us.ibm.com

Update TLS instructions in yaml files and docs.
Specifically, indicate that TLS CA certs and client TLS CA certs do not
need to be configured on every peer and orderer, since peers and orderers
automatically use the TLS CA certs that exist in the channel configuration.
However, additional TLS CA certs can be configured for peers and orderers to
augment the list of TLS CA certs from the channel configuration.

Signed-off-by: David Enyeart <enyeart@us.ibm.com>
@denyeart denyeart requested review from a team as code owners November 17, 2020 21:02
file: tls/ca.crt
# If mutual TLS is enabled, clientRootCAs.files contains a list of additional root certificates
# used for verifying certificates of client connections.
# It is not required to be set, but can be used to augment the set of TLS CA certificates
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is quite right... if you require client auth, and you do not set this, how can you join a peer to a channel? It's only 'not required' once your peer has channels.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think he meant it is not required to be set since the mutual TLS is also not required

@yacovm yacovm merged commit e7b81ba into hyperledger:master Nov 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants