Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

External Chaincode Mutual TLS

未關閉
#625 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
68/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
grpc, java

研究方向

Start by reading ChaincodeBase.getChaincodeServerConfig() and NettyGrpcServer.configureTls(), then trace how client_auth_required and trustCertCollectionFile are applied for an external server. Reproduce the Java chaincode setup with invalid client_key and client_cert values. Done means client authentication is enforced when requested and the invalid client credentials do not permit peer communication.

由索引模型根據 Issue 內容生成。

描述

bug
Description

When using the Java shim as an external chaincode server, setting client_auth_required to true in the packaged connection.json does not appear to enable mutual TLS with the default server configuration.

NettyGrpcServer.configureTls() only requires and validates client certificates when ChaincodeServerProperties.trustCertCollectionFile is set. However, ChaincodeBase.getChaincodeServerConfig() enables TLS and sets the server certificate and key, but does not set that trust-certificate property.

In my test, the peer connected and chaincode communication succeeded even though connection.json contained invalid client_key and client_cert values. I expected the connection to fail if client authentication was required. This is an observation from my Java chaincode setup.

Steps to reproduce
  1. Start a Java external chaincode server with TLS enabled, configuring its server certificate and key but not a trust certificate collection for peer client certificates.

  2. Set client_auth_required to true in the external chaincode package’s connection.json.

  3. Set client_key and client_cert to invalid test values, for example:

    {
      "client_auth_required": "true",
      "client_key": "invalid test key",
      "client_cert": "invalid test certificate"
    }
主要語言
Java
星號
322
分支
210
平均合併
15 小時 16 分鐘
30 天內合併 PR
29

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

hyperledger/fabric-chaincode-java 的其他 Issue

查看 hyperledger/fabric-chaincode-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。