From 33726eb29d292d2a6ffe11199569f72a2a8e491e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ren=C3=A9=20Jeglinsky?= Date: Mon, 15 Jan 2024 11:49:45 +0100 Subject: [PATCH] fix links (#624) * fix links * fix link --- about/features.md | 2 +- guides/data-privacy/pdm.md | 2 -- guides/security/aspects.md | 2 +- 3 files changed, 2 insertions(+), 4 deletions(-) diff --git a/about/features.md b/about/features.md index a848c28a0..a5a843e45 100644 --- a/about/features.md +++ b/about/features.md @@ -234,7 +234,7 @@ Following is an index of the features currently covered by CAP, with status and | [Deploy to/run on _SAP BTP, Cloud Foundry environment_](../guides/deployment/) | | | | Deploy to/run on _Kubernetes_1 | | | | [Deploy to/run on _Kyma_](../guides/deployment/deploy-to-kyma) | | | -| [SaaS on-/offboarding](../guides/deployment/as-saas) | | | +| [SaaS on-/offboarding](../guides/multitenancy/) | | | | [Multitenancy](../guides/multitenancy/) | | | | Health checks | | | diff --git a/guides/data-privacy/pdm.md b/guides/data-privacy/pdm.md index 7a4c44157..df805da12 100644 --- a/guides/data-privacy/pdm.md +++ b/guides/data-privacy/pdm.md @@ -179,8 +179,6 @@ Deploy your application: cf create-service-push ``` -For multitenant-specific information, refer to our [Multitenancy Guide](../deployment/as-saas). - ### Subscribe to SAP Personal Data Manager Service diff --git a/guides/security/aspects.md b/guides/security/aspects.md index 1897f93c9..7a969a2df 100644 --- a/guides/security/aspects.md +++ b/guides/security/aspects.md @@ -131,7 +131,7 @@ Learn more about user model and identity providers here: CAP microservices consume remote services and hence need to be authenticated as technical client as well. Similar to [request authentication](#authenticate-requests), CAP saves applications from having to implement secure setup of service to service communication: -- CAP interacts with platform services such as [Event Mesh](../messaging/) or [SaaS Provisioning Service](../deployment/as-saas) on basis of platform-injected service bindings. +- CAP interacts with platform services such as [Event Mesh](../messaging/) or [SaaS Provisioning Service](../deployment/to-cf) on basis of platform-injected service bindings. - CAP offers consumption of [Remote Services](../using-services) on basis of [SAP BTP destinations](../using-services#btp-destinations). Note that the applied authentication strategy is specified by server offering and resp. configuration and not limited by CAP.