Enable a Connector to communicate with multiple DAPS (Dataspaces) #258
-
|
Currently a Connector can only register to one DAPS, hence only be participant at one dataspace. However it would be essential to be able to participate with one connector multiple dataspaces, hence it is necessary to be able to pass the associated DAPS token and/or the address of the associated DAPS with the corresponding request. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
|
Hello and thank you for the feedback, we will take a look! |
Beta Was this translation helpful? Give feedback.
-
|
After an initial estimate of the changes needed, this idea will be forwarded internally to the respective architecture groups, as multiple components and concepts would need to be addressed than just the IDS-Messaging-Services to implement this feature request. |
Beta Was this translation helpful? Give feedback.
-
|
IDSA internal ideas of having multiple DAPS: https://industrialdataspace.jiveon.com/docs/DOC-2832 (depricated) see new discussion document here: https://github.com/International-Data-Spaces-Association/IDS-ThinkTank/tree/main/ids-daps-federation |
Beta Was this translation helpful? Give feedback.
-
|
Will move it to the discussion section, as this requires conceptual changes that we can't address only here in the context of this repo. (Are there then multiple connector certificates from different DAPS etc.?). |
Beta Was this translation helpful? Give feedback.
-
|
DSA internal ideas of having multiple DAPS: https://github.com/International-Data-Spaces-Association/IDS-ThinkTank/tree/main/ids-daps-federation |
Beta Was this translation helpful? Give feedback.
IDSA internal ideas of having multiple DAPS: https://industrialdataspace.jiveon.com/docs/DOC-2832 (depricated) see new discussion document here: https://github.com/International-Data-Spaces-Association/IDS-ThinkTank/tree/main/ids-daps-federation