hyperledger-fabric-ca

来源： https://stackoverflow.com/questions/58543416/run-intermediate-ca-with-tls-enabled-connection-to-root-ca-refused

问题 Let's take the scenario of 3 equitable organizations, i.e., each organization runs peers and should be equally involved in the ordering process. For me, it feels quite natural to configure those 3 organizations to have an orderer node and some peers, each. However, this setup is highly discouraged . Quote from the FAQ: Question: Can I have an organization act both in an ordering and application role? Answer: Although this is possible, it is a highly discouraged configuration. By default the

问题 I have a single-org setup running with one Fabric CA. CA Server is running with MySQL. I'm using NodeSDK to connect and issue transactions to chaincode. I'm able to set Country, State, Locality, Organisation and Organisation Unit attributes for the peers and orderers. However, when I register and enroll "users" with the Fabric, not all attributes are being set. Only the Common Name and Organisation Unit attributes are set as seen from the certificate file. Following is my snippet for

问题 I know that this may be duplicate issue. I did not find a valid answer. What can the be wrong here. I am trying connect to my fabric network using client application. In my current configuration, admin and user enrollment is successful. But whenever I am trying to query in my peer0, it shows this error. My node verion is 8.9.12 . ccpPath path: /home/hypuser/fabric-samples/servicebook-fabric/connection.json Wallet path: /home/hypuser/fabric-samples/servicebook-fabric/wallet E0930 03:49:55

问题 I want to clear in my mind the use of a MSP, So my question is when a user wants to use a channel for any reason, the local MSP provide him an identity with his private key (in docs said the MSP has a keystore) and after the channel confirm the user using the channel MSP? When CA involved to? 来源： https://stackoverflow.com/questions/53297909/hyperledger-fabric-understanding-msp

问题 I want to use openldap docker container with fabric-ca , I've been searching on internet for a week now. Is there anyone in the community who have tried or implemented ? 回答1: I can't say I have done it myself, but you can configure the Fabric CA to use LDAP. Inside your CA Server Configuration file there is a section related to LDAP. More specifically, you would start by enabling LDAP and pointing to the URL where it is running: ldap: enabled: true url: ldap://<adminDN>:<adminPassword>@<host>

问题 Long time back I have created a composer network by using composer version 0.19.0. Now when I am trying to ping the network using following command getting this error. composer network ping --card admin@tutorial-network output :Error: Error trying to ping. Error: 2 UNKNOWN: identity expired Please help me how to resolve this issue. 回答1: Do you have any other identities registered (and thus have cards in your card store) with your business network which haven't expired ? If you don't then you

问题 I'm trying to connect Hyperledger Fabric CA to an Openldap. The Openldap is set up in local, with a single organisation dc=fabric-ca,dc=example,dc=com And a single user, cn=admin,dc=.../ I have set up a Fabric-CA with following server config : ldap: enabled: true url: ldap://cn=admin,dc=fabric-ca,dc=example,dc=com:000000@☺localhost:389/dc=fabric-ca,dc=example,dc=com userfilter: (dn:%s) tls: enabled: false attribute: names: ["dn"] Converters and maps are irrelevant (so far). The admin exist in

问题 I have created a hyperledger-composer application with an Angular frontend and multi-user authentication. The admin can create a new participant and issue an identity for this participant. Adding the participant to the network works fine. But the second step - issuing an identity for this new participant results in the following error message: "message": "fabric-ca request register failed with errors [[{\"code\":20,\"message\":\"Authorization failure\"}]]", ... see the following screenshots:

问题 Note: I am using the Go SDK, but this should apply to Node, Java, etc. SDKs. I am using a fabric-ca instance as my Certificate Authority, and for a realistic production environment I need to use a secure connection. Based on the config-e2e.yaml example configuration file [1], we should be able to use https in the CA url. Example: certificateAuthorities: org1-ca: url: https://localhost:7054 However, once https is required, the SDK requires that the TLS cert/key filepath is added in the client