![]() The communication between client and balancer, and the communication between balancer and nodes should all be done https. Important note when using load balancers: For more information seeĮdge://flags/#same-site-by-default-cookiesĮdge :// flags/#cookies -without- same - site -must-be-secureĬhange the value for both flags to DISABLE This can be done exclusively for Development and Testing environments, for Chrome up to version 91.Ĭhrome://flags/#same-site-by-default-cookiesĬhrome://flags/#cookies-without-same-site-must-be-secureĬhange the value for both flags to DISABLE. Keep in mind that this affects all sites browsed, not just Bizagi. Change the default behavior on Chrome and Edge browsers with the appropriate flags. You can follow the procedure to set the Work Portal to Work with HTTPSĢ. Our preferred option is to enable HTTPS in all environments (dev, test, prod) with a valid certificate. Specifically, there is a behavioral change in Chrome and Edge for handling cookies that do not explicitly set the SameSite cookie attribute to None.ġ. The mentioned browsers pushed a change that creates a conflict with Bizagi Work Portal when it is not configured to use HTTPS. which would leave your session logged in indefinitely. If you would like to disable the timer, you would enter. If you are using Chrome Update 80 or later or Microsoft Edge 80.0.361.48 or later and you navigate using HTTP and not HTTPS, you may experience an issue where Bizagi's Work Portal displays an error when trying to work on a case.Īll versions in Development and Test environments when running on Google Chrome or Microsoft Edge.īizagi Work Portal using Google Chrome or Microsoft Edge, the following error message Hello Sajan, Under the line vty 0 3, the 'exec-timeout 15 (minutes) 0 (seconds)' command will disconnect your session after 15 minutes of inactivity. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |