The SameSite cookie attribute controls how cookies are used when an endpoint is called from the context of another web application. You can set the default cross-domain, that is, the SameSite behavior of cookies to enhance security and privacy.
Using the SameSite attribute, you can restrict the Set-Cookie HTTP response header to first-party or same-site contexts. This feature is available only in secure contexts (HTTPS) in most browsers.
You can set the SameSite cookie attribute to the lax, strict, and none values. If the SameSite attribute is not specified explicitly, the default cookie value is set to lax.
The ActiveVOS user interface is used in guides that can be embedded in third-party web applications. To embed guides in a third-party web application, you must set the SameSite attribute value to none and not strict. If you do not use guides or use guides only in the ActiveVOS application and not in third-party applications, you can use strict mode for protection. For more information about the SameSite cookie values, see
SameSite cookie values.
A user with the administrator role for the ActiveVOS server can control the SameSite cookie attribute in the following ways:
Set the SameSite cookie attribute for the Set-Cookie header at the proxy level or the load balancer level.
Control the SameSite cookie attribute at the server level through server-specific settings. However, all the servers and versions do not support the SameSite attribute. Tomcat, WebSphere, JBoss, and WebLogic application servers support the SameSite attribute. For more information about the server-specific setting, see the following community article: