作曲家从不同主机请求身份
Composer request identity from different host machine
我正在按照本教程进行修改,以从不同的主机添加组织。
https://medium.com/@mahoney_33893/hyperledger-composer-adding-another-organization-to-an-existing-running-multi-organization-fff5c8104a82
我正在尝试将新组织添加到来自不同主机(例如 Org3)的现有频道。我已经设法将来自 org3 的对等体加入到频道中。我有 org3 运行.
的 CA
然后我使用修改后的连接配置文件创建并导入了 PeerAdmin 卡。
然而,当我 运行 作曲家身份请求时,我收到错误消息错误:无法请求身份。尝试注册用户和 return 证书时出错。错误:注册失败,出现错误 [[{"code":19,"message":"CA 'ca.org1.example.com' does not exist"}]]。请注意,为 org1 运行我的 ca 的端口已打开。
然后我尝试从 org3 中的 ca 获取日志,结果发现 (POST /api/v1/enroll 404 19 "CA 'ca.org1.example.com' does not exist"。为什么我的 ca来自 org3 的 ca 需要与来自 org1 的 ca 通信?为什么它说我来自 org1 的 ca 实际上已经启动并且 运行 不存在?非常感谢任何帮助
当前使用 hyperledger composer,hyperledger fabric v 1.2.1。当前未使用 TLS。
{
"name": "hlfv1",
"x-type": "hlfv1",
"x-commitTimeout": 300,
"version": "1.0.0",
"client": {
"organization": "Org3",
"connection": {
"timeout": {
"peer": {
"endorser": "300",
"eventHub": "300",
"eventReg": "300"
},
"orderer": "300"
}
}
},
"channels": {
"composerchannel": {
"orderers": [
"orderer.example.com"
],
"peers": {
"peer0.org1.example.com": {},
"peer0.org3.example.com":{}
}
}
},
"organizations": {
"Org1": {
"mspid": "Org1MSP",
"peers": [
"peer0.org1.example.com"
],
"certificateAuthorities": [
"ca.org1.example.com"
]
},
"Org3":{
"mspid": "Org3MSP",
"peers": [
"peer0.org3.example.com"
],
"certificateAuthorities": [
"ca.org3.example.com"
]
}
},
"orderers": {
"orderer.example.com": {
"url": "grpc://{{hostmachineurl}}:7050"
}
},
"peers": {
"peer0.org1.example.com": {
"url": "grpc://{{hostmachineurl}}:7051"
},
"peer0.org3.example.com": {
"url": "grpc://{{localmachineurl}}:11051"
}
},
"certificateAuthorities": {
"ca.org1.example.com": {
"url": "http://{{hostmachineurl}}:7054",
"caName": "ca.org1.example.com"
},
"ca.org3.example.com": {
"url": "http://{{localmachineurl}}:9054",
"caName": "ca.org1.example.com"
}
}
}
my docker 创建同级 org3
version: '2'
volumes:
peer0.org3.example.com:
networks:
byfn:
services:
peer0.org3.example.com:
container_name: peer0.org3.example.com
extends:
file: peer-base.yaml
service: peer-base
environment:
- CORE_PEER_ID=peer0.org3.example.com
- CORE_PEER_ADDRESS=peer0.org3.example.com:7051
- CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org3.example.com:7051
- CORE_PEER_LOCALMSPID=Org3MSP
volumes:
- /var/run/:/host/var/run/
- ~/fabric-samples/first-network/org3-artifacts/crypto-config/peerOrganizations/org3.example.com/users/Admin@org3.example.com/msp:/etc/hyperledger/fabric/msp
- ~/fabric-samples/first-network/org3-artifacts/crypto-config/peerOrganizations/org3.example.com/users/Admin@org3.example.com/tls:/etc/hyperledger/fabric/tls
- peer0.org3.example.com:/var/hyperledger/production
ports:
- 11051:7051
- 11053:7053
networks:
- byfn
查看上面的 connection.json
- 我明白为什么它会从 Org1 CA(而不是 Org 3 的 CA)请求:
"certificateAuthorities" 下的这一部分应为 "ca.org3.example.com"(参见下面 //):
"certificateAuthorities": {
"ca.org1.example.com": {
"url": "http://{{hostmachineurl}}:7054",
"caName": "ca.org1.example.com"
},
"ca.org3.example.com": {
"url": "http://{{localmachineurl}}:9054",
"caName": "ca.org1.example.com" // change this line
}
}
您可能还需要检查其他条目。
我正在按照本教程进行修改,以从不同的主机添加组织。 https://medium.com/@mahoney_33893/hyperledger-composer-adding-another-organization-to-an-existing-running-multi-organization-fff5c8104a82
我正在尝试将新组织添加到来自不同主机(例如 Org3)的现有频道。我已经设法将来自 org3 的对等体加入到频道中。我有 org3 运行.
的 CA然后我使用修改后的连接配置文件创建并导入了 PeerAdmin 卡。
然而,当我 运行 作曲家身份请求时,我收到错误消息错误:无法请求身份。尝试注册用户和 return 证书时出错。错误:注册失败,出现错误 [[{"code":19,"message":"CA 'ca.org1.example.com' does not exist"}]]。请注意,为 org1 运行我的 ca 的端口已打开。
然后我尝试从 org3 中的 ca 获取日志,结果发现 (POST /api/v1/enroll 404 19 "CA 'ca.org1.example.com' does not exist"。为什么我的 ca来自 org3 的 ca 需要与来自 org1 的 ca 通信?为什么它说我来自 org1 的 ca 实际上已经启动并且 运行 不存在?非常感谢任何帮助
当前使用 hyperledger composer,hyperledger fabric v 1.2.1。当前未使用 TLS。
{
"name": "hlfv1",
"x-type": "hlfv1",
"x-commitTimeout": 300,
"version": "1.0.0",
"client": {
"organization": "Org3",
"connection": {
"timeout": {
"peer": {
"endorser": "300",
"eventHub": "300",
"eventReg": "300"
},
"orderer": "300"
}
}
},
"channels": {
"composerchannel": {
"orderers": [
"orderer.example.com"
],
"peers": {
"peer0.org1.example.com": {},
"peer0.org3.example.com":{}
}
}
},
"organizations": {
"Org1": {
"mspid": "Org1MSP",
"peers": [
"peer0.org1.example.com"
],
"certificateAuthorities": [
"ca.org1.example.com"
]
},
"Org3":{
"mspid": "Org3MSP",
"peers": [
"peer0.org3.example.com"
],
"certificateAuthorities": [
"ca.org3.example.com"
]
}
},
"orderers": {
"orderer.example.com": {
"url": "grpc://{{hostmachineurl}}:7050"
}
},
"peers": {
"peer0.org1.example.com": {
"url": "grpc://{{hostmachineurl}}:7051"
},
"peer0.org3.example.com": {
"url": "grpc://{{localmachineurl}}:11051"
}
},
"certificateAuthorities": {
"ca.org1.example.com": {
"url": "http://{{hostmachineurl}}:7054",
"caName": "ca.org1.example.com"
},
"ca.org3.example.com": {
"url": "http://{{localmachineurl}}:9054",
"caName": "ca.org1.example.com"
}
}
}
my docker 创建同级 org3
version: '2'
volumes:
peer0.org3.example.com:
networks:
byfn:
services:
peer0.org3.example.com:
container_name: peer0.org3.example.com
extends:
file: peer-base.yaml
service: peer-base
environment:
- CORE_PEER_ID=peer0.org3.example.com
- CORE_PEER_ADDRESS=peer0.org3.example.com:7051
- CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org3.example.com:7051
- CORE_PEER_LOCALMSPID=Org3MSP
volumes:
- /var/run/:/host/var/run/
- ~/fabric-samples/first-network/org3-artifacts/crypto-config/peerOrganizations/org3.example.com/users/Admin@org3.example.com/msp:/etc/hyperledger/fabric/msp
- ~/fabric-samples/first-network/org3-artifacts/crypto-config/peerOrganizations/org3.example.com/users/Admin@org3.example.com/tls:/etc/hyperledger/fabric/tls
- peer0.org3.example.com:/var/hyperledger/production
ports:
- 11051:7051
- 11053:7053
networks:
- byfn
查看上面的 connection.json
- 我明白为什么它会从 Org1 CA(而不是 Org 3 的 CA)请求:
"certificateAuthorities" 下的这一部分应为 "ca.org3.example.com"(参见下面 //):
"certificateAuthorities": {
"ca.org1.example.com": {
"url": "http://{{hostmachineurl}}:7054",
"caName": "ca.org1.example.com"
},
"ca.org3.example.com": {
"url": "http://{{localmachineurl}}:9054",
"caName": "ca.org1.example.com" // change this line
}
}
您可能还需要检查其他条目。