How to add SDM_User scope to the Service Broker for service API access

[ch-sap]

Dear colleagues,

we added the attachments to our CDS service. We want to use the service as API via service broker. Unfortunately, the SDM_User scope cannot be added.

xs-security.json
https://github.tools.sap/erp4sme/partner-reference-application/blob/main-multi-tenant-features/xs-security.json

service broker catalog:
https://github.tools.sap/erp4sme/partner-reference-application/blob/main-multi-tenant-features/broker/catalog.json

Is there any way to solve that issue?

Best regards,
Christine

[yashmeet29]

Hi @ch-sap ,
I didn't understand the issue, can you please elaborate the issue and add some more details on what exactly you are trying to do?

Regards,
Yashmeet

[yashmeet29]

Hi @ch-sap, can you please provide the requested details.

Regards,
Yashmeet

[ch-sap]

Dear Yashmeet,

the service broker is used to consume a service via API. Unfortunately, the SDM attachments are not accessible as the SDM_User scope cannot be assigned to the service broker.

The usage of service broker described more in detail in our Service Broker Tutorial. In our application we access our poetryslamservice via the Service Broker API e.g. to test some actions, update an entity and furthermore. The same we thought would be possible with the SAP Document Management service to create, update or delete an attachment via API using the Service Broker. What I tried was…

1. to add the SDM_User scope to our service broker plan called fullaccess like we did it with the PoetrySlamFull role defined in our (xs-security.json file)
2. Deploy the application in the provider subaccount
3. Registering the service broker in the consumer subaccount where our application is subscribed
4. Creating an instance of the service broker plan fullaccess
   a. Did not work. Got a 400 Bad Request, due to adding the SDM_User scope to the service broker plan fullaccess (step 1).

If step 4 would work successfully it would continue like the following:
5. Creating a service binding in the newly created Service Broker plan instance
6. Receiving a token from the instance service binding credentials with which I could access our poetryslamservice via API to create, update or delete e.g. PoetrySlam events, Attachments of a PoetrySlam event

The above steps are also described in our second Service Broker tutorial which describes how to consume the Service Broker APIs.

So in short the problem that I face, is that I am not sure how to add the SDM_User scope to a Service Broker plan correctly in the mta.yaml (Step 1), so that the instance creation of a Service Broker plan works successfully (Step 4).

Best regards,
Christine

[yashmeet29]

Hi @ch-sap, Kindly schedule a call to discuss on this issue further.

Regards,
Yashmeet

[ch-sap]

Hello Yashmeet,
we tested the issue again and the behaviour and usage of service broker works now correctly.

Best regards.
Christine