Symptom
- OData V2 service bindings delivered with a partner add-on arrive unpublished in non-development provider/subscriber systems.
- Requests to OData V2 endpoints return HTTP 403 Forbidden with the error: "The request has been blocked by UCON".
- OData V4 services from the same delivery work without any additional activation steps.
- Manually publishing the V2 service binding in a development system via ADT makes the service work there, but this is not possible in non-development systems.
Read more...
Environment
- ABAP environment on BTP (SaaS/OEM landscape)
- OData V2 and OData V4 services
- RAP service binding
Keywords
odata v2, 403 forbidden, ucon, service binding, unpublished, rap, abap environment, saas oem, iam app, business catalog, role assignment, adt, endpoint access, authorization , KBA , BC-DWB-AIE-SRB , RAP service binding , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview