## 4.5.1  Set Up SAP S/4HANA Cloud Private Edition as a Content Provider
Set up SAP S/4HANA Cloud Private Edition as a content provider for SAP Build Work Zone, standard edition using the SAP Cloud Connector.
##  Caution
SAP Build Work Zone, standard edition automatically uses SAP Cloud Connector as a proxy to any system connected to it. All paths that you configure in your cloud connector will be reachable via the public internet. Please make sure that you only configure the necessary paths and that your SAP S/4HANA Cloud Private Edition system is properly secured to prevent unauthorized access.
1. Establish trust between your subaccount and your SAP S/4HANA Cloud Private Edition system. For more information, see Cloud Connector.
Take note of the following:
- The section about Configure Principal Propagation.
- Disable the System Certificate for Logon setting to enable principal propagation and basic authentication via the SAP Cloud Connector.
For more information, see Expose Intranet Systems.
2. In your SAP Cloud Connector Administration UI, open the Cloud To On-Premise tab.
3. Create a new system mapping and expose the following paths for the HTTPS protocol:
| Path to fetch...              | Value                                  |
|-------------------------------|----------------------------------------|
| Card manifests and i18n files | /sap/bc/lrep/                          |
| The UI5 App Index             | /sap/bc/ui2/app_index/                 |
| CDM3content                   | /sap/bc/ui2/cdm3/                      |
| CDM2content                   | /sap/bc/http/ui2/flp_content_exposure/ |
Path to fetch...
| Data from OData services    | /sap/opu/odata/   |
|-----------------------------|-------------------|
| Data from OData V4 services | /sap/opu/odata4/  |
##  Note
The paths in the table above are for a default configuration, that covers most use cases. However, from a security perspective, we recommend to restrict the paths further, according to the services that are used in your use case.
For more information, see Set Up Cloud Connector.
4. Create a new mapping for the integration with the Identity Provisioning Service using the following values:
| Field                  | Value                                                                      |
|------------------------|----------------------------------------------------------------------------|
| Back-end Type          | ABAP System                                                                |
| Protocol               | RFC or RFC SNC                                                             |
| Connection Type        | With load balancing (system ID and message server)                         |
| Message Server         | <Your SAP S/4HANA Cloud Private Edition message server host, e.g. ldcsuct> |
| System ID              | <Your SAP S/4HANA Cloud Private Edition system ID, e.g. UCT>               |
| SAProuter              | Leave empty.                                                               |
| Virtual Message Server | ldcsuct                                                                    |
| Virtual System ID      | UCT                                                                        |
##  Note
Using the values in the table above, the value of the internal host would be: ldcsuct:sapmsUCT
5. With the Naming Policy set to Exact Name in the Identity Provisioning service, allow access to the following resources:
- BAPI\_USER\_GETLIST
- BAPI\_USER\_GET\_DETAIL
- PRGN\_ACTIVITY\_GROUPS\_LOAD\_RFC
- PRGN\_ROLE\_GETLIST
For more information, see SAP Application Server ABAP.
6. Open your SAP S/4HANA Cloud Private Edition system to preview and expose your content.
##  Note
- Exposure Version : Version 2 applicable from SAP S/4HANA Cloud Private Edition 2023 onwards. To check that your content exposure was successful, you can use the SAP Gateway Client (transaction /IWFND/GW\_CLIENT ) as follows: Send a GET request to /sap/bc/http/ui2/ flp\_content\_exposure/ and check that you receive as a response, the status code 200.
Value
- Exposure Version : Version 1 applicable for all releases of SAP S/4HANA Cloud Private Edition. To check that your content exposure was successful, you can use the SAP Gateway Client (transaction /IWFND/GW\_CLIENT ) as follows: Send a GET request to /sap/bc/ui2/cdm3/ and check that you receive as a response, the status code 200.
For more information, see Manage Launchpad Content for Exposure.
7. To create a technical service user, open transaction SU01 and as the User Type select Service .
8. Make sure that the technical service user fulfills the prerequisites in Manage Launchpad Content for Exposure.
9. In the My Home Settings , make sure that the business users are assigned the value: Insights Cards .
## Related Information
Integrate SAP S/4HANA Cloud Private Edition