Introduction

This blog post is part of the series covering Principal Propagation in SAP Integration Suite.

As explained in SAP Cloud Integration help page, you can set up Principal Propagation with SAP BTP to forward the identity of a user across several systems and avoid the use of technical users in each of the systems involved.

In that first part we want to provide you an overview of different Integration use cases where Principal Propagation can be applied.

Use Cases

• Propagate identity from an external system to an On-Premise SAP Backend with mediation
  An external system acting as client uses Cloud Integration capability of SAP Integration Suite to consume a Backend service. Depending on the authentication method, SAP API Management might be required.

• Propagate identity from a BTP application to an On-Premise SAP Backend with mediation
  A BTP application acting as client uses Cloud Integration capability of SAP Integration Suite via SAP Destination service to consume a Backend service.

• Propagate identity from a BTP application to an On-Premise SAP Backend without mediation
  A BTP application or service acting as client uses SAP API Management via SAP Destination service to consume a Backend service. The application layer can reside in the same subaccount where API Management was setup or can be hosted in a separate subaccount.

• Propagate identity from an external system to SuccessFactors with mediation
  An external system acting as client uses Cloud Integration capability of SAP Integration Suite to consume the SuccessFactors OData API. Depending on the authentication method, SAP API Management might be required.

• Propagate identity from a BTP application to SuccessFactors with mediation
  A BTP application acting as client uses Cloud Integration capability of SAP Integration Suite via SAP Destination service to consume the SuccessFactors OData API.

• Propagate identity from a BTP application to S/4HANA Cloud without mediation
  A BTP application acting as client uses SAP API Management via SAP Destination service running in the same subaccount to consume a service running on S/4HANA Cloud.

• Propagate identity from an external system to S/4HANA Cloud with mediation
  An external system acting as client uses Cloud Integration capability of SAP Integration Suite to consume a service running on S/4HANA Cloud.

Summary

In this blog post we have tried to cover all (or at least the most important) scenarios where you can make use of Principal Propagation utilizing SAP Integration Suite. In future we might update this blog post with additional use cases.