Closed alzcurda closed 2 years ago
I have same problem. I tried to change the network in docker-compose.yml of Broker to 'testbed' in hope, the broker can connect to DAPS, when both are in the same docker-network, but nothing works. Anyone knows a solution?
Is the broker working for you without daps validation? If yes then please confirm we can be clear then it's a DAPS issue.
thanks for quick answering, yesterday I installed the testbed new from the beginning and now it works... maybe I messed up with the certificates..
thanks for quick answering, yesterday I installed the testbed new from the beginning and now it works... maybe I messed up with the certificates..
Could you tell me what certificates did you use?
Keystore (isst-brokerkeystore.jks) and server.key+server.crt
thanks for quick answering, yesterday I installed the testbed new from the beginning and now it works... maybe I messed up with the certificates..
Could you tell me what certificates did you use?
I use the certificates testbed5 for a new connector and now it works
Which certificate was missing?
Which certificate was missing?
nothing, I changed the truststores of DAPS and broker, but this was unnecessary, and something went wrong... fortunately I found the video of IDSA-Winterdays, where the testbed was demonstrated
So 5.0.0-Snapshot of the broker is working for you?
I use the broker from testbed-repo, its broker-core-4.2.8-SNAPSHOT
We are running some tests with the IDS Broker open source implementation and we are running into problems when trying to test the multipart endpoints using the Postman collection available with the documentation.
We have a local deployment of the broker based on the latest docker image but we are using the default Fraunhofer DAPS server (https://daps.aisec.fraunhofer.de/v2/). We are using a dummy certificate generated by the Fraunhofer DAPS for the Trusted Connector implementation as the broker's X509 certificate. We generated a DAT manually with this certificate by launching the Trusted Connector.
For instance, when testing {{connectorUrl}}/infrastructure with the following body:
We get the following response indicating that the token value is invalid:
The internal logs of the broker show the following exception and stacktrace:
Our question is: how do we generate a valid DAT from the Fraunhofer DAPS to use in testing the IDS Broker endpoints? Which certificate should be used for the broker? Is it possible to do that manually or are the DATs only generated when a connection from the IDS connector is made to the Fraunhofer DAPS?