SDK login not working in New Teams for GCC High customers

[Happy202121]

Hello,

We discovered that, for GCC High customers, the Teams JS SDK authentication module in is not working the same with New Teams as it does with Teams Classic.

In Teams Classic, the GCC High user opens our app, clicks a sign-in button, then an embedded browser opens to handle the authorization and authentication.

In New Teams, the GCC High user opens our app, clicks a sign-in button, then the default browser opens a new tab to try and handle the authorization and authentication. The resulting request has the wrong cookies and fails as a result.

Here's what we're using:

microsoftTeams.authentication.authenticate({
url: loginUrl, width: 820, height: 620, successCallback: function(result) {
console.log('Login Successfully: ' + JSON.stringify(result)); that.reloadUserContext(); }, failureCallback: function(reason) {
console.log('Login failed: ' + reason);

[jekloudaMSFT]

Hi @Happy202121, I'm sorry you've run into this. Can you please share the microsoft-teams-library-js version your app uses?

[KaratLee]

@jekloudaMSFT @Happy202121 microsoft-teams-library-js version: @microsoft/teams-js@1.8.0

[jekloudaMSFT]

Hi @Happy202121 @KaratLee, I haven't been able to reproduce this issue with my own Teams application. Could you please follow the instructions here to enable client side logging and then reply to this with the client logs you see when the auth page is opened in the browser? Can I also know if you receive a Login Successfully: or Login failed: log when this occurs?

[KaratLee]

@jekloudaMSFT We got a prompt that the URL could not be opened: Login failed: URL was unable to be opened in embedded browser. (Use Microsoft gov account to access Zoom For GCCH)
Cc @Happy202121

[KaratLee]

@jekloudaMSFT This is the installation package used by Microsoft gov environment customers. If you use the Microsoft gov environment account to access any app on the Microsoft Teams new client, you should be able to see this problem.

[KaratLee]

Hi @jekloudaMSFT is there any progress on this?

[jekloudaMSFT]

Hi @KaratLee, I'm still investigating this issue and will raise it with Teams. Based on the logs, I suspect the issue may be a CSP violation causing the site to open in browser vs a new Teams window. Since the Teams URL for GCC high is gov.teams.microsoft.us, does gov.teams.microsoft.us need to be added to the frame-ancestors allowed by https://applications.zoomgov.com?

[KaratLee]

@jekloudaMSFT Thanks for your response. We'll try your suggestions, but this process works fine in Microsoft Teams classic

[KaratLee]

Hi @KaratLee, I'm still investigating this issue and will raise it with Teams. Based on the logs, I suspect the issue may be a CSP violation causing the site to open in browser vs a new Teams window. Since the Teams URL for GCC high is gov.teams.microsoft.us, does gov.teams.microsoft.us need to be added to the frame-ancestors allowed by https://applications.zoomgov.com?

@jekloudaMSFT We followed your suggestion, but the problem is not solved. Can you help check it?

[KaratLee]

@jekloudaMSFT Any updates?

[jekloudaMSFT]

Hi @KaratLee thanks for the update, I will try to repro in GCCH environment and get back to you. Do you know what the source of the ERR_CONNECTION_REFUSED and 500 (Internal Server Error) errors is? I'm asking because it looks like they're occurring after Teams tries to open the new window

[KaratLee]

@jekloudaMSFT
The 500 error appears before clicking login, so it should not be related to the current problem.

[jekloudaMSFT]

Hi @KaratLee, thanks for your patience. I was able to repro the issue with a test app in the GCCH environment. I'm raising this with the Teams team and will provide another update soon

[KaratLee]

Thanks, looking forward to the update notification.
Cc. @Happy202121

[jekloudaMSFT]

Hi @KaratLee @Happy202121, the Teams desktop team is working on a fix for this. I'll let you know when we have an ETA on the fix being available.

[Happy202121]

Thanks @jekloudaMSFT, do you know which Teams client version will include this fix?