I came across some issues/inconsistencies with the Testbed installation guide and collected them.
the mentioned directory in the CA README does not exist -> should be changed to
cd CertificateAuthority
the command to create a sub CA is wrong. Correct is
python3 pki.py subca create --CA "Test CA" --common-name [Sub CA name]
before the 2nd step of the device certificate creation it should be mentioned, where the created key pair is located, namely in CertificateAuthority/data/cert.
Otherwise it is not clear where to find them.
the last step of fileing the certificates to the components refers to a non existing folder ../../../DataspaceConnector/src/main/resources/conf. I think it should refer to the two DataspaceConnectors within the testbed:
cp {CERT_FILENAME}.p12 ../../../DataspaceConnectorA/src/main/resources/conf and
cp {CERT_FILENAME}.p12 ../../../DataspaceConnectorB/src/main/resources/conf
Edit: Currently, I am not able to assign the issue so I use the mention functionality: @aitorce @jfernandezsqs
I came across some issues/inconsistencies with the Testbed installation guide and collected them.
the mentioned directory in the CA README does not exist -> should be changed to
cd CertificateAuthority
the command to create a sub CA is wrong. Correct is
python3 pki.py subca create --CA "Test CA" --common-name [Sub CA name]
before the 2nd step of the device certificate creation it should be mentioned, where the created key pair is located, namely in
CertificateAuthority/data/cert
. Otherwise it is not clear where to find them.the last step of fileing the certificates to the components refers to a non existing folder
../../../DataspaceConnector/src/main/resources/conf
. I think it should refer to the two DataspaceConnectors within the testbed:cp {CERT_FILENAME}.p12 ../../../DataspaceConnectorA/src/main/resources/conf
andcp {CERT_FILENAME}.p12 ../../../DataspaceConnectorB/src/main/resources/conf
Edit: Currently, I am not able to assign the issue so I use the mention functionality: @aitorce @jfernandezsqs