You can find docker file of Fabric peers here: https://github.com/hyperledger/fabric/blob/release-1.4/images/peer/Dockerfile.in Best regards, Artem Barger.

#fabric #fabric-peer #fabric-orderer #fabric-ca

The peer are emitting the error logs as:

#fabric-ca #fabric

Hi Gari, To test it out, in the CA config file, i set the expiration to 1h and before the certificates expired i reenrolled the `msp` and `tls cert` again with the `--csr.keyrequest.reusekey` flag in

#fabric-ca #fabric

If you use the Fabric CA client v1.5.0, there is an option to reuse your existing key when issuing the reenroll command. You need to add the `--csr.keyrequest.reusekey` flag to your reenroll command.

#fabric-ca #fabric

Hey Chris, Thank you for following up! I will give it a try. One hack I have tried - backup the ledger data, and tear down the network. And then get the fabric network up and running again, in process

#fabric-ca #hyperledger-fabric

Hi Neeroz, Use this to convert your pem certs to base64: export FLAG=$(if [ "$(uname -s)" == "Linux" ]; then echo "-w 0"; else echo "-b 0"; fi) cat <insert path to .pem here> | base64 $FLAG I have don

#fabric-ca #hyperledger-fabric

I am on fabric v2.3 Anyone here has completed this step/process of renewing the certificates in order to continue submitting the transactions from farbic client sdk? All i can find in the docs is just

#fabric-ca #fabric

I followed that path, and seems like it's not a straight-forward to update the tls-certificates. I pulled the latest config block using the peer channel fetch config and decoded it into json file to c

#fabric-ca #hyperledger-fabric

You are most welcome, happy to help.

#fabric-ca #hyperledger-fabric

Hey Chris, Thanks a ton! This definitely points in the right direction.

#fabric-ca #hyperledger-fabric

Hi Neeroz, Great questions! See my answers below. The default expiry is 1 year, but this can be configured by altering the expiry field (expressed in hours, so 1 year = 8760 hours). For security reaso

#fabric-ca #hyperledger-fabric

While renewing/reenrolling what all do we need to do. I mean is there a standard way of doing this? I am on fabric v2.3. This following are straight from the `test-network` fabric sample When we get t

#fabric-ca #hyperledger-fabric

As I recall, the issue here is that in order to override the PKCS11 section of BCCSP, you actually need to make sure that the fields exist in your fabric-ca-server-config.yaml file first.

#fabric-ca

Hello i am trying to configure Fabric-CA with softHSM and facing the below: Error: Failed to get BCCSP with opts: Could not initialize BCCSP PKCS11: Invalid config. It must not be nil. i downloaded th

#fabric-ca

Hi Gari Singh, Thanks for the reply. I was unable to use ORDERER_GENERAL_AUTHENTICATION_NOEXPIRATIONCHECKS=true and --tlsHandshakeTimeShift options in 1.4.0 version. Can you suggest how to renew my or

#fabric #fabric-ca #tls #hyperledger-fabric

You need to use 1.4.3 or later

#fabric #fabric-ca #tls #hyperledger-fabric

Hi Keerthi, I am using 1.4.0 version, Is this option available in 1.4.0 version? Even I was trying to set this ORDERER_GENERAL_AUTHENTICATION_NOEXPIRATIONCHECKS=true env variable in my orderer contain

#fabric #fabric-ca #tls #hyperledger-fabric

Stephano, you can give EJBCA a try. That can be your authoritatively CA you’re looking for. It is open source and you can easily issue set of certificates (root/intermedite/end ca + user certs) direct

#signcerts #interoperability #fabric-ca #x509

People have used directly used certificates that were not issued by a Fabric CA as credentials within a Fabric network. Luckily, there's really no magic here. You will need to set up the membership se

#signcerts #interoperability #fabric-ca #x509

Hello Community, I'm working on a use case where I need to use certificates, which bind resources to identities, that have been already issued by an Authoritative CA with the Fabric Network I'm develo

#signcerts #interoperability #fabric-ca #x509