Having looked at different extensibility and integration scenarios for SAP Build Work Zone already, one aspect is shared across most or even all scenarios. How can the user authentication with the integrated business application be handled securely? As outlined in previous lessons, the SAP BTP connectivity service plays a critically important role in ensuring that such a secure connection can be established. While the default choice (for example, when creating a UI Integration card) is likely to have a direct connection from SAP Build Work Zone<> SAP BTP <>(SAP) business application, there are cases requiring more complex, enterprise grade integration patterns.
Understanding Different Back End Integration Scenarios
Instead of leveraging a direct connection, there can also be integration setups that leverage principal propagation with SAP BTP to forward the principal (identity of a user) across several connections in a complex system landscape. This helps to avoid using technical users in each of the systems involved.
This lesson covers several integration use cases where principal propagation can be applied.
A BTP application, acting as a client, uses the cloud integration capability of SAP Integration Suite via SAP Destination service to consume a back end service.
A BTP application or service acting as a client uses SAP API Management via SAP Destination service to consume a back end service. The application layer can reside in the same subaccount where API Management was set up, or can be hosted in a separate subaccount.
A BTP application acting as client, uses Cloud Integration capability of SAP Integration Suite through SAP Destination service to consume the SAP SuccessFactors OData API.
A BTP application, acting as the client, uses SAP API Management through SAP Destination service running in the same subaccount to consume a service running on SAP S/4HANA Cloud.