The CSR subject common name must equal the enrollment ID about docker-compose-files HOT 4 CLOSED

can u report this problem to the fabric-sdk-py project?

https://jira.hyperledger.org/browse/FAB-4623?jql=project%20%3D%20FAB%20AND%20status%20in%20(%22In%20Progress%22%2C%20%22To%20Do%22)%20AND%20component%20%3D%20fabric-sdk-py

Thanks!

from docker-compose-files.

Sure. But where do you want me to report it, fabric-sdk-py on github or https://jira.hyperledger.org? If it is https://jira.hyperledger.org, how can I get an account to create an issue? Since when I tried to create a new issue, I got the following message.

You are not authorized to perform this operation. Please log in.
Close this dialog and press refresh in your browser

Not a member? To request an account, please contact your JIRA administrators.

from docker-compose-files.

Accroding to this website, sdk and fabric-client communicate with fabric-server through rest api, the param test_tem should be A PEM-encoded string containing the CSR (Certificate Signing Request) based on PKCS #10. Is it means that I need to register a new identity with fabric-client manually, then use this identity's private key to pem-encoded CSR, like the following string:

csr:
  cn: admin2
  names:
    - C: US
      ST: "North Carolina"
      L:
      O: Hyperledger
      OU: Fabric
  hosts:
   - hostname
  ca:
    pathlen:
    pathlenzero:
    expiry:

then use the new pem file to replace the old one?

from docker-compose-files.

After reading the source code of fabric-sdk-java's unit test, it looks like fabric-sdk-python hasn't been finished yet. Generating key pair and pem are missing. Will use fabric-sdk-java instead.

from docker-compose-files.