Solution
1. Our preferred option is to enable HTTPS in all environments (dev, test, prod) with a valid certificate.
You can follow the procedure to set the Work Portal to Work with HTTPS
2. Change the default behavior on Chrome and Edge browsers with the appropriate flags. Keep in mind that this affects all sites browsed, not just Bizagi. This can be done exclusively for Development and Testing environments, for Chrome up to version 91.
For Chrome type in the address bar:
chrome://flags/#same-site-by-default-cookies
chrome://flags/#cookies-without-same-site-must-be-secure
Change the value for both flags to DISABLE. For more information see
https://support.google.com/chrome/thread/26291731?hl=en

For Edge
edge://flags/#same-site-by-default-cookies
edge://flags/#cookies-without-same-site-must-be-secure
Change the value for both flags to DISABLE

3. Downgrade Chrome to 78.0.4147.105 or earlier
4. Use another browser, such Firefox
Important note when using load balancers:
The communication between client and balancer, and the communication between balancer and nodes should all be done https.
|