Since version 80, Chrome, and later Safari, introduced a new model for cookie security. This mode is designed to introduce security controls around availability of cookies to third party sites, through a setting called SameSite
. For more detailed information, see this article.
The default value of this setting (SameSite=Lax
) might cause authentication between AEM instances or services to not work. This is because the domains or URL structures of these services might not fall under the constraints of this cookie policy.
In order to get around this, you need to set the SameSite
cookie attribute to None
for the login token.
The SameSite=None
setting is only applied if the protocol is secure (HTTPS).
If the protocol is not secure (HTTP), then the setting is ignored and the server will show this WARN message:
WARN com.day.crx.security.token.TokenCookie Skip 'SameSite=None'
You can add the setting by following the below steps:
http://serveraddress:serverport/system/console/configMgr
None
, as shown in the image belowlogin-token
cookies will have the None
attribute set and will be included in cross-site requests.