Federated Catalog and IH Integration: Clarifying Token Management and Access Control

[albert-lopez]

Hello,

I’m looking at the provided example for the Federated Catalog and I’m not sure how the federated catalog can work with the consumer’s IH. In the transfer-01-negotiation fetch-catalog example, the catalog request is made through the consumer connector (management/v3/catalog/request). Correct me if I am wrong, but I believe that the connector is responsible for obtaining the token from IH to grant the provider access to the consumer’s IH. However, in the case of querying the federated catalog, the v1alpha/catalog/query API is called directly, without using the connector. In this case, is it the client’s responsibility to obtain the token to grant access to its IH instead of the connector? Is there any API available to obtain this token?

Additionally, is there any protection in place to authorize the federated catalog to perform crawling on the Target Catalog Nodes? How is this done?

Thank you for your help and insights on this topic!

[albert-lopez]

Hi, could anyone please help clarify my question? I would really appreciate it!

[ndr-brt]

A general suggestion is to go through the MinimumViableDataspace sample project, it should give you all the answers you are looking for