客户ca服务器DB
我正在构建一个 Hyperledger Fabric 区块链应用程序（docker 容器），其中我还创建了一个应用程序网关（docker 容器），其中使用 Node js 作为后端服务与其进行交互。
令我惊讶的是，我亲眼目睹了以下案例： 我已经注册了新用户，并使用网络的 CA 通过应用程序网关和官方 Fabric SDK 注册了他们，并将它们存储在 Fabric 钱包中。我意识到它们存储在与 Fabric ca docker 容器的 /etc/hyperledger/fabric-ca-server/ 目录下不同的 Fabric-ca-server.db 中。
我的意思是，当我尝试通过 cli 列出身份时，我得到的身份为零，因为它们是通过 SDK 注册的。当我尝试从 SDK 注册相同的身份时，我收到了用户已注册的常见消息。
但我无法找到该 Fabric-ca-server.db 的存储位置，该数据库读取应用程序网关（SDK）
I am building a Hyperledger Fabric blockchain application (docker containers) where I have created also an application gateway (docker container) with node js to interact with it as a backend service.
For my surprise I have witnessed the following case:
I have registered new users and enrolled them through the application gateway and the official Fabric SDK using the CAs of the network and stored them in the Fabric Wallet. And I realized that they are stored in a different fabric-ca-server.db than the one that lives under the /etc/hyperledger/fabric-ca-server/ directory of the fabric ca docker container.
What I mean is that when I tried to list the identities through the cli I got zero identities since they were registered through SDK. And when I tried to register the same identities from the SDK I got the usual message of user is already registered.
But I was not able to find where this fabric-ca-server.db is stored that reads for the application gateway (SDK)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
DB文件可以使用以下路径在CA容器中找到，
您会发现Docker组合文件中也提到了此路径。
The DB file can be found in the CA container using the following path
You will find that this path is also mentioned in the docker compose file.
上面答案中所述的正确路径是fabric CA容器内的目录！
我的错误是，通过应用程序 SDK，我只注册了一些管理员，而没有注册他们。这只是颁发证书，而不将它们添加到实际的数据库中。在我注册了一些用户并注册它们之后，我可以在 docker 容器中的数据库中查看它们。
The correct path as is stated in the above answer is the directory inside the fabric CA container!
My mistake was that through the application SDK I was only enrolling some admins without registering them. And this was only issuing certificates without adding them to the actual db. After I registered some users and registered them I was able to view them all in the db that is in the docker container.