Questions About Connector and Identity Hub Interaction #4932
-
Hey, I have a few questions regarding the interaction between the Identity Hub (IH) and the Eclipse EDC Connector. How does the Connector determine which Identity Hub it should communicate with? Any guidance or documentation you can point me to would be greatly appreciated. Thanks in advance! Best regards |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
The connector doesn't directly interact with "its own" IdentyHub. Rather, it interacts with the SecureTokenService, to obtain ID tokens. This SecureTokenService may be embedded directly in the IdentityHub (default case), or it could be a standalone service (not recommended, only in special use cases). The STS URL, client-id and client secret alias are configuration values ( However, there are ofc interactions with the counter-party's IdentityHub, because the connector obtains the VCs using the Presentation Flow. To do that, the verifying connector inspects the DID document (contained in the ID token) of the proving connector and parses the For a more comprehensive overview check out the Decentralized Claims Protocol and for a practical example, check out the MinimumViableDataspace sample project. |
Beta Was this translation helpful? Give feedback.
The connector doesn't directly interact with "its own" IdentyHub. Rather, it interacts with the SecureTokenService, to obtain ID tokens. This SecureTokenService may be embedded directly in the IdentityHub (default case), or it could be a standalone service (not recommended, only in special use cases). The STS URL, client-id and client secret alias are configuration values (
edc.iam.sts.oauth.[token.url,client.id,client.secret.alias]
).However, there are ofc interactions with the counter-party's IdentityHub, because the connector obtains the VCs using the Presentation Flow. To do that, the verifying connector inspects the DID document (contained in the ID token) of the proving connector and…