Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retrieve public MSP information from channel config for fabric driver resolvers #413

Open
davidkel opened this issue Oct 10, 2022 · 2 comments

Comments

@davidkel
Copy link
Contributor

For the fabric driver resolvers you might have an entry such as

    endpoint:
      resolvers: 
      - name: approver
        domain: org1.example.com
        identity:
          mspID: Org1MSP
          path: /home/dave/github-cloned/fabric-smart-client/samples/fabric/iou/testdata/fabric.default/crypto/peerOrganizations/org1.example.com/users/approver@org1.example.com/msp/signcerts/approver@org1.example.com-cert.pem

Currenly the path either refers to the the public cert of the signer or the nodes public msp (ie without any private keys). Access to the public MSP is required in case the signer certificate is sanitized by fabric and thus doesn't match the certificate stored in the MSP file system.

It would be better to obtain the public MSP from the channel configuration instead

@adecaro
Copy link
Contributor

adecaro commented Dec 2, 2022

Hi @davidkel , I think it is not possible to do what the issue asks because this MSP contains the approver's PK which is not available on the ledger. The MSPs on the ledger contains only the root and intermediate CA certs.

If you agree, I will close this issue.

@adecaro adecaro closed this as completed Dec 2, 2022
@adecaro adecaro reopened this Dec 2, 2022
@davidkel
Copy link
Contributor Author

davidkel commented Dec 7, 2022

ok, then I think we need to remove path support to individual pem files otherwise others will hit the same problem where fabric might change the pem

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

No branches or pull requests

2 participants