MSAL vs. Microsoft Teams
As ADAL hasn't been touched in over two years now, I have migrated my application to MSAL. Sadly enough the Teams docs are still ADAL based. I have an application that is working fine outside Microsoft Teams. Once I embed it as an app inside Microsoft Teams, two things happen: MSAL's acquireTokenSilent method, which returns a promise, fails silently without any possibility to know what happened. This has been raised before, many times: https://github.com/OfficeDev/TrainingContent/issues/606 https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/222 https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/470 I tried to enable MSAL's debug logging info. Working fine stand-alone; inside Teams: not one log message. There seems to have been https://github.com/OfficeDev/TrainingContent/blob/master/Teams/04%20Fundamentals%20of%20Microsoft%20Teams/Lab.md#exercise3 with MSAL's acquireTokenSilent in it, but that probably worked because it was launched from the config screen (or elsewhere) and not from the tab. So on what location would acquireTokenSilent work? Should we move it to such an authentication popup to get it to work (far less silent though).
Showing an external WebApp in Teams tab - Authentication issue
We have some important company websites - Angular applications that are using ADAL/MSAL or no authentication at all - that our users are using very often. Currently they have the browser open + MS Teams and use both tools. I thought its nicer to show our App inside an MS Teams tab, to use Teams as a "browser" and to make life easier for our users. What I did is simply creating a test app that I deployed to our tenant. The app is having the web address to our external web app as a content-uri in a tab: Now our app is appearing in the Teams client on the left side after installation: If I launch this app our page appears a short time and then reloads for a hundred times at once. What I would expect is a redirection to the MS page to login, to get a token for the user (like it works in Chrome) I tried out different scenarios: In the Teams-Browser app: - Everything works perfectly In the Teams Desktop app - that everyone is using: - Using ADAL with redirection method => Like described above - Using MSAL with interactionType: InteractionType.Popup => Tries to open "about" in the MS store, because there is no app available. The popup blocker cannot be a problem, because I have a button for login (user interaction) so I expect a window opening where I can login, but I get this: I can never press ok - why is not a browser used? - Using MSAL with interactionType: InteractionType.Redirect => Blank page - Using an app without any authentication => Works as expected, the page is shown I am now confused why this is happening. The teams iframe does allow popups explicitly if I inspect the iframe with DevTools. Everything we want is to display one external page with MSAL or ADAL authentication enabled. Another approach I tried: Using a "real" teams App that uses SSO. Once I have the token I pass it to the iframe with a #token=ey.... Howevery, this approach also does not work and the page is blank. I think I am already to complicated in how I think. There must be an easy solution for this problem. Any proposals are highly appreciated.
Silent SSO with MSAL
Hi the Teams documentation and samples use adal.js for authentication, as in https://docs.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/authentication/auth-silent-aad. Can anyone confirm that the Teams SDK and samples will move to msal.js - and if so, when? The latest thread about MSAL is already half a year old..
