From 687a1a4e34a4716c4ab4ee1e8a2eec79e3d86416 Mon Sep 17 00:00:00 2001 From: Moritz Schubert <35040095+mcnoat@users.noreply.github.com> Date: Tue, 6 May 2025 14:41:03 +0200 Subject: [PATCH] typo correction --- .../connectivity-scenarios-1e4b878.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/1-connectivity-documentation/connectivity-scenarios-1e4b878.md b/docs/1-connectivity-documentation/connectivity-scenarios-1e4b878.md index 459f968..a60ece4 100644 --- a/docs/1-connectivity-documentation/connectivity-scenarios-1e4b878.md +++ b/docs/1-connectivity-documentation/connectivity-scenarios-1e4b878.md @@ -60,7 +60,7 @@ Some common *principal propagation* scenarios for communication between an SAP B ## Scenario: Cloud to On-Premise -In this scenario, you want to perform calls from your SAP BTP application to a target application located in your local *on-premise* network. While the basic procedures are similar to the *cloud-to-cloud* scenario \(including some configuration that is specific to on-premise communication\), this connection type requires the Cloud Connector as additional component, to be installed an managed within your local on-premise network. The Cloud Connector provides a secure tunnel for communication between your local apps and SAP BTP. +In this scenario, you want to perform calls from your SAP BTP application to a target application located in your local *on-premise* network. While the basic procedures are similar to the *cloud-to-cloud* scenario \(including some configuration that is specific to on-premise communication\), this connection type requires the Cloud Connector as additional component, to be installed and managed within your local on-premise network. The Cloud Connector provides a secure tunnel for communication between your local apps and SAP BTP. > ### Note: > A commonly used authentication method is *principal propagation* \(also known as *user propagation*\), which lets you propagate the identity of the logged-on user to the target application.