Symptom
- The usage of OAuth2SAMLBearerAssertion in SAP Build Apps results in a "401 Unauthorized" error.
- Relevant error message: "Response details: { "status": 401, "headers": { "content-type": "application/json; charset=utf-8", "date": "Mon, 06 Oct 2025 14:05:55 GMT", "x-correlation-id": "823d7571-f358-4dd9-738b-92e06c60ca94", "x-powered-by": "Express", "x-vcap-request-id": "823d7571-f358-4dd9-738b-92e06c60ca94", "strict-transport-security": "max-age=31536000; includeSubDomains; preload;", "connection": "close" }, "data": { "error": { "code": 401 } }}"
Read more...
Environment
SAP Build Apps
Keywords
OAuth2SAMLBearerAssertion, 401 Unauthorized error, SAP Build Apps, destination configuration, SAML Assertion Provider, subaccount trust certificate, Token Service URL, trusted certificates, HTML5.ForwardAuthToken, sapSalesAndServiceCloud , KBA , CA-LCA-ACP , SAP Build Apps , 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