Cookie Use When Site Framed In
Posted: Sat Sep 03, 2022 8:30 am
Hi,
We have an application written outside of LANSA running on one domain that frames in some WAM pages. The domains do not match. Eg. *.app1.com and *.app2.com. In the latest version of Chrome it appears it enforces that unless the SameSite=none is returned with the Set-Cookie header then the cookie won't be stored and therefore is not passed back to the WAM. This same issue is in Edge. Firefox is okay.
My question is can I modify the Set-Cookie header that is returned by LANSA? If so, how do I do this? If I can't can the framing application do something to tell the browser to accept the cookie and pass it to the WAM?
We have an application written outside of LANSA running on one domain that frames in some WAM pages. The domains do not match. Eg. *.app1.com and *.app2.com. In the latest version of Chrome it appears it enforces that unless the SameSite=none is returned with the Set-Cookie header then the cookie won't be stored and therefore is not passed back to the WAM. This same issue is in Edge. Firefox is okay.
My question is can I modify the Set-Cookie header that is returned by LANSA? If so, how do I do this? If I can't can the framing application do something to tell the browser to accept the cookie and pass it to the WAM?