[Bug]: Cant login with symantec login due to contextIsolation

[osatien]

Can you reproduce this bug on the Microsoft Teams web app (https://teams.microsoft.com)?

NO

Describe the bug

I cant login with the default source due to contextIsolation=false. I think it is because my sso page needs contextIsolation to true. After i change the contextIsolation: false to true i can login. the sso page appears ok. The problem should be later when using the app. can you place make something to fix this? i mean open login with contextisolation true and later the app with false.

What package are you using?

deb

Version

2.7.0

Reproduction steps

1. download code and without modifying start
2. cant login
3. modify contextIsolation to true
4. can login (i suppose application wont work well)
...

Expected Behavior

1. download and work 
2. perhaps open login with contextIsolation true and remove after login if it is possible
3.
...

Debug

ELECTRON_ENABLE_LOGGING=true teams-for-linux --logConfig='{"transports":{"console":{"level":"debug"}}}'


i will upload this logs after the good and bad one

Additional context

lognew_bad.txt
lognew_ok.txt

[ismael-triage-bot]

👋 Thanks for reporting this issue!

Note: You mentioned this bug also occurs on the Microsoft Teams web app. This suggests the issue may be with Microsoft Teams itself rather than Teams for Linux. You could also report it to Microsoft Feedback Portal. That said, we'll still take a look — there may be something we can do on our end.

This might be related to a known issue:

• Oauth Services require internal Electron window — This appears similar because both issues relate to how Electron handles authentication flows for external services (OAuth/SSO) within its internal window, and the bug report specifically mentions con Ensure that the application is configured to open authentication links within the Electron window rather than an external browser, and investigate if contextIsolation` settings are impacting this beh

• Blank Page at Login — This might be related because an inability to log in due to contextIsolation preventing the SSO page from functioning correctly could manifest as a blank or non-responsive login screen. Check if the login page is failing to load or interact due to contextIsolation settings. If a blank page appears, try the workaround mentioned in the bug report (adjusting contextIsolation) to see

• Unable to log in, stuck on a blank screen after entering credentials — This could be connected because the reported inability to log in due to contextIsolation might result in the application getting stuck on a blank or non-functional screen after attempting to enter c If you are stuck on a blank screen after entering credentials, investigate if contextIsolation settings are preventing the SSO flow from completing. The user's workaround of changing `contextIsolati

These suggestions are based on our documentation and may not be exact matches.

This issue might be related to existing discussions:

Recently resolved issues that could be relevant:

• [Bug]: Can't login because can't load Symantec's MFA (Content Security Policy violations and JavaScript errors) #1543 — "[Bug]: Can't login because can't load Symantec's MFA (Content Security Policy violations and JavaScript errors)" (Resolved) — This issue appears very similar as it also reports a login failure specifically related to Symantec's MFA and security policies (Content Security Policy violations), which aligns closely with the new
• [Bug]: Login fails for non-microsoft provider #2093 — "[Bug]: Login fails for non-microsoft provider" (Resolved) — This issue describes a general problem with login failing for non-Microsoft providers, which could encompass the Symantec login issue reported in the new bug. The contextIsolation problem might be a
• MS SSO doesn't open the external page to login with company account #1299 — "MS SSO doesn't open the external page to login with company account" (Resolved) — This issue reports that the external page for SSO login doesn't open, which might be related to the contextIsolation problem preventing the Symantec SSO page from loading correctly or behaving as ex

If one of these matches your issue, consider adding your details there instead.

Tip: You might also find helpful information in our Troubleshooting Guide.

---

I'm a bot that helps with issue triage. Suggestions are based on documentation and may not be exact. A maintainer will review this issue.

[IsmaelMartinez]

Hi @osatien , the bot did find a few pointers worth looking at. The #1543 has a workaround.

Reading at the workaround, it might be worth adding that contextIsolation to support your use case but I will have a look at the logs/details to see if we can just fix it (I got low expectations)

[osatien]

that is what i do ... i used to fix with that version but as you removed that parameter i cant use this. and that version (2.0.19) is not more in the versions to download. now i can edit the code and modify it for myself, but it would be better if you could fix, or add contextIsolation to all (parameter to enable just for login)

i asked gemini to fix this, try to put contextisolation just for login and remove after login and did something, although the first time after login didnt work well (the tray bar icon didnt work well) but after login with cookies ok it worked (i think that the context isolation is something that broke the tray bar, it fixed too something to the ipc i dont know so well, that can be related too)

[IsmaelMartinez]

Hi , can you check if this build fixes it? #2330 (comment) If it does then I should be able to merge and pre-release maybe as early as today. If it doesn't then I will add back the contextIsolation workaround. Thanks in advance!

[osatien]

sorry but not ... it is not working :(

this is what i see and
attached are the logs, i think they can be helpfull becuase i see some info related to security constraints

log.txt

[IsmaelMartinez]

can you try the latest version of the build in #2330 (comment) ? It should work, but if it doesn't I will revert this and previous changes and add the workaround. Thanks again