Application Load Balancer - third-party cookies in Google Chrome - Stickiness cookie
1
I'm using AWS Application Load Balancer with Stickiness cookie generated by the aws Load balancer.
This year (2024), Google Chrome will introduce the "Privacy Sandbox" and will disable third-party cookies: https://developers.google.com/privacy-sandbox/3pcd
This is a big problem for us right now as well. If you are using an ALB from within a frame of a third party site (we are required to do so, as a plugin to LTI compliant learning management systems like Canvas), your AWSALB-0 cookies will not be sent in chrome when CHIPS is active. I tried setting the cookie myself (i.e. returning a response with the AWSALB cookie's name/value and the Partitioned=True attribute from my target app) but it isn't making it back to the browser, the ALB is rewriting it and sending it without the attribute. This means that ALB stickiness is broken for 1% of our users on chrome, and thus our app is too.
AWS 官方已更新 1 年前
This is a big problem for us right now as well. If you are using an ALB from within a frame of a third party site (we are required to do so, as a plugin to LTI compliant learning management systems like Canvas), your AWSALB-0 cookies will not be sent in chrome when CHIPS is active. I tried setting the cookie myself (i.e. returning a response with the AWSALB cookie's name/value and the Partitioned=True attribute from my target app) but it isn't making it back to the browser, the ALB is rewriting it and sending it without the attribute. This means that ALB stickiness is broken for 1% of our users on chrome, and thus our app is too.