SAP Knowledge Base Article - Preview

3652985 - Odata Receiver adapter Metadata call Header configuration

Symptom

During message processing, the OData adapter internally makes a $metadata call before reaching the actual endpoint. However, the headers set for the OData endpoint call are not included in the metadata call. This discrepancy may lead to failures since the metadata call also requires these headers for successful execution.

For instance, if you've deployed an on-premise OData service via APIM, and the API Proxy requires an API-key header for authentication in the metadata call, the absence of this key will cause the metadata call to fail. Consequently, the call to the actual endpoint will also be unsuccessful.


Read more...

Environment

  • SAP Integration Suite
  • Cloud Integration

Product

Cloud Integration all versions ; SAP Integration Suite all versions

Keywords

Odata adapter, header configuration, API key authentication, missing header, 428 error, CPI, APIM, metadata header, CSRF token, allowed headers, wildcard configuration. , KBA , LOD-HCI-PI-CON-OD , OData Adapters , 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.