From 5d9fa91c6608b79be3fa50e130c1deb3df9078f3 Mon Sep 17 00:00:00 2001 From: Steffen Waldmann Date: Fri, 24 Oct 2025 14:59:05 +0200 Subject: [PATCH 1/3] Simplify multitenancy configuration --- guides/multitenancy/index.md | 19 ++++--------------- 1 file changed, 4 insertions(+), 15 deletions(-) diff --git a/guides/multitenancy/index.md b/guides/multitenancy/index.md index e303290108..9cbd7f3623 100644 --- a/guides/multitenancy/index.md +++ b/guides/multitenancy/index.md @@ -79,6 +79,9 @@ cds add multitenancy "requires": { "[production]": { "multitenancy": true + }, + "[with-mtx]": { + "multitenancy": true } } } @@ -721,25 +724,11 @@ cds add mta ``` ```sh [Kyma] -cds add helm,containerize -``` - -::: - -::: details Add xsuaa redirect for trial / extension landscapes -Add the following snippet to your _xs-security.json_ and adapt it to the landscape you're deploying to: - -```json - "oauth2-configuration": { - "redirect-uris": ["https://*.cfapps.us10-001.hana.ondemand.com/**"] - } +cds add kyma ``` ::: -[Learn more about configured BTP services for SaaS applications.](#behind-the-scenes){.learn-more} - - ::: code-group ```sh [Cloud Foundry] From a80c69ac8145787827c8f713d051ae0e219084d5 Mon Sep 17 00:00:00 2001 From: Steffen Waldmann Date: Fri, 24 Oct 2025 15:01:27 +0200 Subject: [PATCH 2/3] Remove "Behind the Scenes" --- guides/multitenancy/index.md | 18 ------------------ 1 file changed, 18 deletions(-) diff --git a/guides/multitenancy/index.md b/guides/multitenancy/index.md index 9cbd7f3623..ab4b624109 100644 --- a/guides/multitenancy/index.md +++ b/guides/multitenancy/index.md @@ -1264,24 +1264,6 @@ The main task for the MTX sidecar is to serve `subscribe` and `upgrade` requests The CAP services runtime requests models from the sidecar only when you apply tenant-specific extensions. For Node.js projects, you have the option to run the MTX services embedded in the main app, instead of in a sidecar. - -### Behind the Scenes { #behind-the-scenes} - -With adding the MTX services, your project configuration is adapted at all relevant places. - -Configuration and dependencies are added to your _package.json_ and an _xs-security.json_ containing MTX-specific scopes and roles is created. {.node} - -Configuration and dependencies are added to your _.cdsrc.json_ and an _xs-security.json_ containing MTX-specific scopes and roles is created. {.java} - -For the MTA deployment service dependencies are added to the _mta.yaml_ file. Each SaaS application will have bindings to at least three SAP BTP service instances. - -| Service | Description | -| ------------------------------------------------------------ | ------------------------------------------------------------ | -| [Service Manager](https://help.sap.com/docs/SERVICEMANAGEMENT/09cc82baadc542a688176dce601398de/4e19b11211fe4ca2a266d3fdd4a72188.html) (`service-manager`) | CAP uses this service for creating a new SAP HANA Deployment Infrastructure (HDI) container for each tenant and for retrieving tenant-specific database connections. | -| [SaaS Provisioning Service](https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/3971151ba22e4faa9b245943feecea54.html) (`saas-registry`) | To make a SaaS application available for subscription to SaaS consumer tenants, the application provider must register the application in the SAP BTP Cloud Foundry environment through the SaaS Provisioning Service. | -| [User Account and Authentication Service](https://help.sap.com/docs/CP_AUTHORIZ_TRUST_MNG) (`xsuaa`) | Binding information contains the OAuth client ID and client credentials. The XSUAA service can be used to validate the JSON Web Token (JWT) from requests and to retrieve the tenant context from the JWT.| - -