We are configuring our Spartacus application with SSR in SAP Commerce Cloud. Also we used the IP Filter Set to secure our endpoints in SAP Commerce Cloud, (JS Applications, Backoffice and API).

Spartacus部署在Commerce Cloud上。

SAP Commerce Cloud的API endpoints被IP Filter set保護。

We had experienced problems serving the request using SSR in our Spartacus application, after debugging the application we have confirmed the problem is in the whitelist of the API. When the whitelist is applied for a set of IP Filter set, spartacus is unable to access the API in SSR mode.

Spartacus無法在SSR模式下訪問API

We had removed the restriction in API, allowing anyone to access the API to test our Spartacus SSR application and in this case the application is served using SSR.

去掉IP filter set后，問題消失。

We need to know which is the IP Range of the Spartacus application to add it in the whitelisting utility for the API endpoint.

需要將SAP Spartacus Storefront在SSR模式下運行時的IP range添加到白名單。

All these endpoints are inside the SAP Cloud.

We enabled SSR for Spartacus according to this documentation: https://sap.github.io/spartacus-docs/server-side-rendering-in-spartacus/

On local machine it is working with a production build and the cloud API.

In the manifest.json for the js-storefront the enableSSR property is set to true and deployed to the SAP Commerce Cloud.

The SSR is not working at the moment on SAP Commerce Cloud and we have no possibility to debug it or get logs for that.

The different services of the Conforama DEV / STG System running in the CCV2 Cloud are restricted and only whitelisted for some IPs (Customer, Some Webservices).

The problem with that is, that when the Request to the OCC API endpoint is done by the Spartacus SSR, the IP is then not the one from the actual user, e.g. myself. but the IP from the Server, where the JS Storefront is running on.
Because that IP is not whitelisted, the Apache Server returns a 403 error and the SSR rendering never completes with Rendering.

There is an open CCV2 Ticket (https://cxjira.sap.com/browse/MTD-12988) to fix this issue and ignore any IP restrictions when the request comes from an internal ip (=SSR Request).
For now, we where able to find a workaround by adding the IP of the Storefront as a restriction. Of course, that is only a temporary solution, as this IP could change.

action item

We need to find a better way to allow the internally allow the SSR pod to access the API pod.

創作挑戰賽新人創作獎勵來咯，堅持創作打卡瓜分現金大獎

總結

以上是生活随笔為你收集整理的关于SAP Spartacus在服务器端渲染模式和SAP Commerce Cloud API白名单的问题的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。