kofigumbs / multi

Create custom, lightweight macOS apps from websites
GNU General Public License v3.0
1.29k stars 40 forks source link

Disabling Cross Site Tracking in Safari for Microsoft Teams #98

Open LaurDr opened 2 years ago

LaurDr commented 2 years ago

As of know you can use Teams in Safari, but you need to disable Prevent-Cross site tracking. Is there any way we could also disable this in Multi so Teams can finally work with Multi?

Originally posted by @ratonhat in https://github.com/kofigumbs/multi/issues/75#issuecomment-1287834445

kofigumbs commented 1 year ago

I looked into this a little today, and it's not clear to me what Teams is calling "Prevent-Cross site tracking". That's the name of a Safari feature, and not something that translates directly to WebKit.

The only request filtering that Multi does is based on the blocklist, and someone else already observed that removing the blocklist doesn't change this behavior. I suspect the issue is in whatever sniffing Microsoft uses to detect "tracking"—though it could also be that there's a WebKit config I haven't discovered that's blocking some content.

simondsmason commented 1 year ago

This is an issue for me also. I use Web Catalog at present because Teams does work in their browser engine. I need to access multiple Teams environments simultaneously and using this approach is better than the native MS option which forces you to switch from one to the other - effectively logging out of the last one each time. I don't know how (or why) they are blocking Safari access. It is not like their web application runs that well in other browsers anyway.

rightsaidfred99 commented 1 year ago

Isn't it cookie related? like the website is teams.microsoft.com but they probably use a cookie from one of their 1000 domains? Correct me if I'm wrong! But disabling the "precent cross site tracking" just enables cookies from any domain which MS seems to be happy with when loading teams.

ptrkhh commented 1 year ago

Also same issue here, cannot use MS Teams. We could try isolating the issue by deleting the cookies on a properly logged-in device one by one perhaps