To ensure a smooth integration of the webclient into your website using the SDK, you must adhere to the following requirements:
- Ensure that the top-level domain name (eTLD+1) of both the cluster serving up the SDK and the hosting site match. This matching prevents third-party cookie restrictions. For instance, if your cluster DNS name is zfe.company.com, the web page embedding the webclient site must also be hosted at company.com or a subdomain of it, such as portal.company.com.
- Both URLs must use the same URL scheme or protocol, either HTTPS or HTTP. Consistency in URL schemes is essential for proper functioning.
- While it's recommended to adjust the SameSite cookie attribute to None for cross-site deployments, it's not necessary if both the webclient and the embedding page are using HTTPS and are in the same eTLD+1. However, keep in mind that this requirement may change in the future, especially with the anticipated changes from Google regarding third-party cookie blocking. Refer to the Deployment Guide for detailed instructions on making this adjustment.