問題

CMS OCC WS Endpoint don’t add User information in URI so all CMS Restriction based on user or usergroups are not working. is there any fix existing to get a ASM fully functionnal with Spartacus ?

回復

The short answer is that there is no fix for this in Spartacus since OCC does not support it.

As you pointed out, the CMS endpoints from OCC don’t accept a userId parameter that defines the user for which the request applies. During an ASM customer emulation session, the user for which the request applies is the customer, which is different from the authenticated user (the customer support agent). For the CMS endpoints below, which Spartacus relies on for CMS, the requests use the authenticated user only: /{baseSiteId}/cms/components /{baseSiteId}/cms/components/{componentId} /{baseSiteId}/cms/pages /{baseSiteId}/cms/pages/{pageId} /{baseSiteId}/cms/sitepages

Since OCC does not accept a userId parameter in the CMS OCC endpoints, it is not possible for an emulated customer to trigger CMS rules and restrictions during an ASM emulation session via CMS OCC. Therefore it is not supported in Spartacus.

總結

以上是生活随笔為你收集整理的关于SAP Commerce Cloud OCC API url里不包含user信息的问题的全部內容，希望文章能夠幫你解決所遇到的問題。

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