By default, LogicNets does not use third-party cookies. However, to support running LogicNets inside an iFrame, our system allows you to change the same-site attribute to None or None; Partitioned through system configuration. See System Configuration Security Settings for information on how to do this. 

If you change the same-site attribute to None, the LogicNets cookies behave as third-party cookies. This means a browser may block them when LogicNets runs in an iFrame. The user may be asked to log in again, even if that user is logged into the main site.

Unpartitioned vs. Partitioned Cookies

Cookies can be unpartitioned or partitioned, and the difference is in how browsers store, access, and clear cross-site contexts; from an iFrame, for example. Browsers share unpartitioned cookies across all sites, enabling cross-site tracking, while partitioned cookies (Cookies Having Independent Partitioned State, or CHIPS) are restricted to the top-level site that set them. This enhances user privacy.

As all major browsers moves away from third-party cookies, partitioned cookies are required to maintain functionality like single sign-on in iFrames while maintaining user privacy. Partitioned cookies are keyed to the top-level site--partition--where they are created; for example, a cookie named session set on site-a.com within an iFrame on publisher.com is only sent back to site-a.com when it is in an iFrame on publisher.com. Site-a.com cannot access it if it is embedded in other-site.com, protecting user privacy.