Skip to content

fabric: apply ordering TLS defaults to configured orderers (#1112) - #1336

Open
malsomesh9 wants to merge 1 commit into
hyperledger-labs:mainfrom
malsomesh9:somesh/issue-1112-ordering-tls
Open

fabric: apply ordering TLS defaults to configured orderers (#1112)#1336
malsomesh9 wants to merge 1 commit into
hyperledger-labs:mainfrom
malsomesh9:somesh/issue-1112-ordering-tls

Conversation

@malsomesh9

Copy link
Copy Markdown
Contributor

What changed

  • apply ordering.tlsEnabled to configured Fabric orderers: entries instead of only discovered channel orderers
  • apply ordering.tlsClientAuthRequired to configured orderers: entries as the default client-auth setting
  • preserve explicit per-orderer tlsEnabled, tlsDisabled, and tlsClientSideAuth opt-ins

Why

Issue #1112 is aligning FSC TLS behavior with the documented configuration model. Before this change, the ordering TLS overrides were only used when deriving orderer connections from channel config, while statically configured fabric.<network>.orderers silently ignored them.

Impact

Configured orderers now follow the same TLS defaulting rules documented for the ordering service. Users can disable or enable TLS for ordering separately from peer traffic, and can enable ordering mTLS centrally without repeating the setting on every configured orderer.

Validation

  • go test ./platform/fabric/core/generic/config/... ./platform/fabric/core/generic/membership/...

Signed-off-by: Somesh Mal <malsomesh9@gmail.com>
@malsomesh9
malsomesh9 marked this pull request as ready for review April 26, 2026 19:09
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.

1 participant