Data offering: access policy configuration, the CONSUMER does not appear as an option.

Carlos Pacheco Perelló
2026-03-31T12:14:51Z

Hello,

We are trying to achieve a simple data transfer between a SIMPL data provider and a SIMPL consumer. We have deployed and configured the agents, and after onboarding both parties, we attempted to publish a data offering on the provider's side. (Authority 2.4.1, Common 2.4.2, Consumer 2.4.1, Provider 2.4.1)

Initially, the published data was not visible in the catalogue for either the provider or the consumer. On the provider side, we resolved the issue by following the guidance from simpl/simpl-open/development/data1/sdtooling-api-be#1 _“Data offerings created on SD Tool are not visible.”_ However, the problem persists on the consumer side.

The main issue seems to be that when publishing the data, the policy configuration **does not provide an option for the consumer to search for or access the data offering**. This appears to be the same problem described in simpl/simpl-open/development/agents/data-provider#4

![Captura de pantalla_7-1-2026_141451_sd-ui.dataprovider01.ibtourismdataspace.org.jpeg](/uploads/01d76b4b6b347428dc93262a90249929/Captura_de_pantalla_7-1-2026_141451_sd-ui.dataprovider01.ibtourismdataspace.org.jpeg)

The only solution we have considered so far is to create a new identity attribute Consumer_P, which then appears as an available option when defining access policies for the data offering.

![Captura de pantalla_7-1-2026_141623_sd-ui.dataprovider01.ibtourismdataspace.org.jpeg](/uploads/ba19baadbd09a080971f6f5d15f93676/Captura_de_pantalla_7-1-2026_141623_sd-ui.dataprovider01.ibtourismdataspace.org.jpeg)

However, since onboarding has already been completed, this new attribute **cannot be added to the already deployed consumer agent or assigned to existing roles**, due to what appears to be synchronization issues, or at least we do not know how to do so. This seems to be the same problem as described in simpl/simpl-open/development/agents/consumer#1

**Update:** After running an ECHO on the consumer side, we realized that the new attribute does appear in the consumer database attributes. The actual problem lies in the **impossibility of assigning this attribute to the consumer**, as the onboarding process has already been completed, or at least we are not aware of how to do so.

Our questions are:

1. Is there an option to enable the consumer’s attribute in the data offering policies for an already deployed agent?
2. If not, is there a way to add the new attribute to an already deployed consumer agent?
3. Or is the only option to redeploy the consumer agent?

Thank you in advance for your help.

Best regards,