Tested on IBP version: 2.1.3
Ensure that you have the following:
jq
Ensure that you have completed the previous tutorial and has not deleted crypto-config
folder
Copy the CA configuration template. You will need this JSON file to override the CA configuration in IBM Blockchain Platform
cp ica.json.template ica.json
In ica.json
, fill in the following:
ca.ca.keyfile
- the Identity ICA's key in base64 formatca.ca.certfile
- the Identity ICA's certificate in base64 formatca.ca.chainfile
- the Identity ICA's chain certificates in base64 formattlsca.ca.keyfile
- the TLS ICA's key in base64 formattlsca.ca.certfile
- the TLS ICA's certificate in base64 formattlsca.ca.chainfile
- the TLS ICA's chain certificates in base64 format
To retrieve ca.ca.keyfile
:
export FLAG=$(if [ "$(uname -s)" == "Linux" ]; then echo "-d"; else echo "-b 0"; fi)
cat crypto-config/peerOrganizations/org1.example.com/ca/ica.identity.org1.example.com.key | base64 $FLAG
To retrieve ca.ca.certfile
:
cat crypto-config/peerOrganizations/org1.example.com/ca/ica.identity.org1.example.com.cert | base64 $FLAG
To retrieve ca.ca.chainfile
:
cat crypto-config/peerOrganizations/org1.example.com/ca/chain.identity.org1.example.com.cert | base64 $FLAG
To retrieve tlsca.ca.keyfile
:
cat crypto-config/peerOrganizations/org1.example.com/tlsca/ica.tls.org1.example.com.key | base64 $FLAG
To retrieve tlsca.ca.certfile
:
cat crypto-config/peerOrganizations/org1.example.com/tlsca/ica.tls.org1.example.com.cert | base64 $FLAG
To retrieve tlsca.ca.chainfile
:
cat crypto-config/peerOrganizations/org1.example.com/tlsca/chain.tls.org1.example.com.cert | base64 $FLAG
If required, you can modify the rest of the configurations by referring to Fabric CA Server Config.
In IBM Blockchain Platform, override the default configuration by using the previously modified JSON file