Frontend boundary
Exposing a CAP service to a frontend that does not live inside BTP. Authenticating an externally-hosted app against an XSUAA or IAS-protected service, what replaces the approuter when the frontend is on a CDN, destinations from outside BTP, principal propagation, and multitenancy under edge caching.
Overview
Not covered: It stops at frontends the platform hosts. Everything the paved road provides — routing, token exchange, tenant resolution — comes from the Application Frontend service, so a frontend hosted anywhere else takes all of it back on: authenticating against XSUAA or IAS from outside, replacing the approuter, reaching destinations, and keeping tenants apart under edge caching.
Built into @sap/cds
No community artifact is documented here.
Artifacts
Content
Group by
Piece, what it offers
From Inbox to Quotation: An AI-Assisted Sales Workbench in React on SAP CAPFrom Inbox to Quotation: An AI-Assisted Sales Workbench in React on SAP CAPA Devtoberfest 2026 session walking live through a sales workbench that turns an incoming customer e-mail into a quotation in S/4HANA, built as a React UI on CAP. It shows the filterable request inbox, the extracted configuration properties with a confidence indicator per characteristic, the variant configurator rendered in React from a JSON schema the configuration service returns, and the link from a derived value back to the place in the e-mail it was read from; the stated reason for the stack is that CAP keeps authentication, destinations and deployment the same in every project, which is where frontend boundary holds. The inbox grows while a user works because a CAP WebSocket plugin pushes new requests into the list — WebSocket.SAP Developers, published 2026-10-09
CAP, CORS and custom headersCAP, CORS and custom headersWhat CAP itself does about CORS, and where it stops. The starting point is a colleague's request and a deliberate constraint: @sap/approuter has full CORS support, but the author wanted to know what the CAP server offers on its own and how to extend it. Ends up covering preflight requests and custom servers, which is the mechanism a frontend hosted outside BTP actually runs into.published 2024-04-11
Details
Coverage
For your agent
- Ref
capability:frontend-boundary- JSON
- /capabilities/frontend-boundary.json
- MCP
- Connecting an agent