Symptom
Support of 2-legged OAuth authentication flow for OData API.
Environment
SAP Datasphere
Resolution
- Currently, consuming exposed data in third-party clients, tools, and apps via an OData service requires a three-legged OAuth2.0 flow with type authorization_code.
- An enhancement request was already raised for this point: Improvement Request Details - Customer Influence (sap.com)
See Also
SAP Help Portal Documentations:
Keywords
Authentification authentication failed service API consume 2-lagged three-legged OAuth2.0 , KBA , DS-BB-ODATA , To address issues related to Odata consumption API , Problem
Product
SAP Datasphere all versions
SAP Knowledge Base Article - Public