Application Router with Separate Authorization Models
The concept name is not defined in the provided sources, and the sources only describe specific communication scenarios — Principal Propagation and Technical Communication with tightly coupled developments on SAP BTP — without defining an explicit named concept. There is insufficient information in the provided sources to write a grounded definition for an unnamed or undefined concept.
Docs explaining this concept
Prerequisites
- Concept Cloud Foundry application deployment on SAP BTP The concept name is not defined in the provided sources, so a grounded definition cannot be written. The sources cover topics such as the [Cloud Foundry Environment](https://help.sap.com/docs/btp/sap-business-technology-platform/9c7092c7b7ae4d49bc8ae35fdd0e0b18?locale=en-US&state=PRODUCTION&version=Cloud) on SAP BTP and related developer tasks like binding service instances and logging on via the CLI, but none of them define a concept identified as "undefined." Please provide a valid concept name and relevant sources to generate an accurate definition.
- Concept SAP Application Router The concept provided is **undefined** and the supplied sources do not contain sufficient information to produce a grounded, accurate definition. The sources cover topics such as configuring redirect URLs for browser logout, destination options in `xs-app.json`, and various SAP BTP tutorials, but none of them define a specific named concept that can be documented here. Please provide a valid concept name and relevant source snippets so a definition can be written.