具有自定义环回实现的 Hyperledger Composer

debugcn 发表于 Dev

莱昂纳多·卡拉罗

我想创建一个自定义环回服务器来处理与用户关联的超级账本作曲家卡。

在我想要创建的场景中，有不同的用户能够在区块链中执行交易。

用户应该能够登录到 Web 门户并提交交易。

这要求 Web 门户的凭据（用户名和密码）存储在数据库中，而卡片则存储在服务器的文件系统中。

一旦用户登录，服务器应识别他并选择与该特定用户相关联的对应卡。

有谁知道这可能是实现这一点的最佳方法？

Paul O'Mahony

you might well consider using a Cloud store location for your business network cards, that contain the blockchain identities (but your chosen strategy overrides that, eg cards persisted to a REST server instance) - a business network card (for the designated user) is then accessible to that application user (once authenticated, see item 4 below) to be able to connect to, then interact with, the protected business network, and ledger - as the specified identity. An example of one cloud strategy is shown here - more info on cloud wallets here
You would create participants in Composer (the class(es) for which are defined in your model file) in the business network, and issue identities through Composer (mapped to the participant above) - or indeed from your CA server, as an administrator (eg the user goes through some application user registration process then activates the account, their blockchain identity, via a link to their email id etc etc or as suits) . Your Composer identity (in the business network) could possibly map to the web portal user id in some way (meaning: whether you want that to be direct or indirect, you'll know your security architecture better).
Some of what you are asking about is answered in this Stack -> Hyperledger Composer Web application user authentication
您显然会使用身份验证策略来验证您的 Web 应用程序用户 - 例如，如果您的应用程序使用 Composer REST API 与区块链上的业务网络进行交互。有关示例，请参阅此 Google OAUTH2（基于客户端身份验证）教程 -> https://hyperledger.github.io/composer/latest/tutorials/google_oauth2_rest。