Forum Discussion

heri_klue's avatar
heri_klue
Copper Contributor
Dec 26, 2023

New Teams Desktop unable to use third-party oauth provider when embedding site

By using the Website app, our users were previously able to have our site (app.klue.com) in a tab, either on the desktop, mobile or teams web app. Previously, we use the authentication flow as detail...
microsoft teams
Meghana-MSFT's avatar
Meghana-MSFT
Former Employee
Dec 28, 2023
Thank you for reporting this, we will look into this and get back to you.
Meghana-MSFT's avatar
Meghana-MSFT
Former Employee
Jan 03, 2024
We have the following response from engineering team - The external auth flow is already supported in T2.1. The external auth flow is only available to Platform Apps and cannot be used from the Website tab. We would need more details from the developer along with repro steps for the issue they are describing because I can't imagine how something like that would be possible even in T1 using the Website tab.

Could you please share the above details.
  • heri_klue's avatar
    heri_klue
    Copper Contributor
    Jan 16, 2024
    Thanks Meghana-MSFT

    To reproduce
    1. In the web app or classic Teams, go to a channel in Teams, and then click + (Add a Tab) button.
    2. Choose "Website" when prompted, then specify "https://app.klue.com" as URL. Click "Save"
    3. Click Login. Feel free to email me `heri _at_ klue.com` for test credentials. The login works on classic Teams or web app but would not work for the new Desktop app

    Do you know if there are plans to support external auth flow for Website tab in T2.1?
    • Meghana-MSFT's avatar
      Meghana-MSFT
      Former Employee
      Jan 30, 2024
      The Website tab is not going to work the same in the New Teams Client as it did in the Classic Teams Client. Website tab will be deprecated. Hence there aren't any plans to support external auth flow for Website tab in T2.1.
      • Meghana-MSFT's avatar
        Meghana-MSFT
        Former Employee
        Feb 01, 2024

        Please find the below response from engineering team- 

        Looks like this is happening because the Klue app is making some assumptions about undocumented behavior of Teams that are broken in Teams 2.1 resulting in the divergent behavior. Specifically, they have code in their website that tries to determine if they are being rendered in Teams to change the way login is handled:

        In Teams 2.1, the name of the Website tab frame is "platform-website-tab" instead of "embedded-page-container" so the check that the Klue app is doing returns false. They should update this logic to also check for "platform-website-tab"; however, long term it would be best if they figured out how to channel customers to their dedicated Klue app:

         

        Since the Website tab is on a path to deprecation:

        https://devblogs.microsoft.com/microsoft365dev/upcoming-updates-to-loading-websites-in-teams-tabs

         

  • Meghana-MSFT's avatar
    Meghana-MSFT
    Former Employee
    Jan 05, 2024

    heri_klue - Could you please share above details?

Resources