Microsoft Teams: Issue logging into third party teams integrations/apps

[austin2118ace]

Avoid duplicates

• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

v7

What Operating System are you using?

Windows

Operating System Version

Windows 10 Education 10.0.19045 Build 19045

What arch are you using?

x64

Last Known Working Ferdium version

No response

Expected Behavior

Since the 'open links within Ferdium' setting is set, when the service/app presents its login page and the user clicks 'Login', the login page for the website should open over teams and allow the user to authenticate. This happens both within the teams 'Apps' toolbar and when trying to add the app/service as a tab within teams chats and pages.

Actual Behavior

When trying to authenticate or login to a third party service (Priority Matrix in this specific case), Microsoft Teams does respect the "open links in Ferdium" setting. The authentication page for this app opens in the system's default browser. When logging in within the browser, this service is unable to callback and inform the teams app that the login was successful. If I add Priority Matrix as a "custom website" it opens the authentication page within Ferdium and successfully logs in.

One solution I found was the 'sandbox' the website and teams together so teams could access the token/cookie for the website, but it would be easier if teams would just open the login page temporarily and allow users to authenticate.

Steps to reproduce

1. Add teams as a service and login
2. Open the apps "store/page" and install Priority Matrix
3. Open priority matrix and wait for the login page to appear; users are given the option of logging in with email or Microsoft
4. Clicking either login link opens the login page in the system browser
5. User authenticates in the system browser and redirects to a 'callback' URL that cannot reach teams
6. Service does not log in

Debug link

https://debug.ferdium.org/d8b9aa2a-81e9-46e1-a6c7-91e7082e231e

Screenshots

No response

Additional information

No response