Open jfernandezsqs opened 2 years ago
I had the same error, and I solved it by changing the permissions of the certificates. When the DAPS cannot use the certificates it is because the certificate's permissions are too strict. With "chmod" instruction you should solve the bug.
I changed the certificate permissions of the components (giving read, write and execution permissions) and have also changed line 102 of the docker-compose.yml
file.
I have used the following:
image: registry.gitlab.cc-asp.fraunhofer.de/eis-ids/broker-open/core:5.0.0
With these changes it fails to register the connector at the Metadata Broker.
Currently, it is not possible to insert the Broker private key into the broker-core container. As a workaround in the IDS-testbed we are currently building a new Broker container with the correct Java Keystore inside so that it works correctly with the rest of components (DSC and DAPS). This is not the suitable way because it is tested a different container than the one that is published in the official MDB repository.
It has been tried the solution described here but it does not validate the IDS-testbed DAPS. This is the error obtained when trying to register the DSCA to the MDB.