Hi, today Online will change its own ASP.NET session cookie from using SameSite=Lax to SameSite=None, as informed in email to application owners.
For our apps we're already working on using SameSite=None, since WE are a third-party when running inside a webpanel in SuperOffice. In that case I totally see why SameSite=None is needed.
However, I don't understand what problem changing SuperOffice's SameSite from Lax to None. What is the scenario where that fixes an issue..? Is that for when SuperOffice is hosted inside an iframe on another site? Does it have anything to do with Service, Customer Center or Chat? Or something with SuperID?
I'm sure there is a good reason, and chances are we're going to do this change for our Onsite customers, I just don't see why.
What am I not getting?