International-Data-Spaces-Association/IDS-testbed

is it possible separate TestBed components?

Closed this issue · 1 comments

I have a doubt, is it possible to have DAPS, consumer connector, provider connector in three separate machines?
I am not sure if someone has made this test. I do that, but when I am trying to consume provider's artifact I get some errors. I have the following configuration:
- Provider machine:
I put in etc/host: IP_omejdn_machine omejdn
And only "ConnectorA" docker compose running.
- Consumer machine
(etc/hosts)
IP_omejdn_machine omejdn
IP_connector_provider_machine connectora
And "ConnectorB" docker compose running
Omejdn machine
Only omejdn
OMEJDN docker-compose running

And .....
I get the following error in provider side:

connectora | 2023-02-27T16:16:34,624 [https-jsse-nio-8080-exec-6] INFO - Received incoming message. [code=(IMSMEI0059)]
connectora | 2023-02-27T16:16:34,697 [https-jsse-nio-8080-exec-6] INFO - Requesting public key of token issuer. [url=(https://omejdn/auth/jwks.json), kid=(543d303f4f81a43bb484767429aa4119cd0e9c92f13042d2db28f3598a0aa8e4), code=(IMSCOI0051)]
connectora | 2023-02-27T16:16:34,705 [https-jsse-nio-8080-exec-6] ERROR - Exception while requesting public key from token issuer! [code=(IMSCOE0148), message=[omejdn: Temporary failure in name resolution]]
connectora | 2023-02-27T16:16:34,706 [https-jsse-nio-8080-exec-6] ERROR - An unhandled exception has been caught. [exception=(publicKey is marked non-null but is null)]
connectora | java.lang.NullPointerException: publicKey is marked non-null but is null

And in consumer side:
connectorb | 2023-02-27T16:17:54,438 [https-jsse-nio-8081-exec-6] WARN - Received response but response-code not in 200-299. [code=(IMSMEW0046), response-code=(500)]

connectorb | 2023-02-27T16:17:54,449 [https-jsse-nio-8081-exec-6] DEBUG - Received invalid ids message. [exception=(String could not be parsed, could not find a boundary!)]

Any help?
Thanks.

I have solved it, it was networks problems between differents containers.