Unable to get past Login screen in Teams

[Coffi007]

I have completed the steps to create the EOC app. I am unable to get past the login screen in Teams. I am attaching the log from Teams web browser. Unauthorized.txt

[v-asshrirao]

@Coffi007, thanks for reaching out to us. We will need more information to help you with this. Step 1: Can you please confirm if deployment was successful? You can validate this by navigating to, Resource Group > Overview > Deployment

Step 2: If deployment is successful, validate if authentication setup is configured correctly. Step 3 from Deployment Guide. Resource Group > App Service > Configuration

Can you also share manifest files with us for further troubleshooting on this issue.

[Coffi007]

Yes deployment was successfully completed. I verified everything from step three is configured correctly. I had already shared the log from the Teams web browser. I am attaching it again in a note pad.

From: v-asshrirao @.> Sent: Wednesday, August 23, 2023 7:52 PM To: OfficeDev/microsoft-teams-emergency-operations-center @.> Cc: Rob Lundquist @.>; Mention @.> Subject: Re: [OfficeDev/microsoft-teams-emergency-operations-center] Unable to get past Login screen in Teams (Issue #134)

@Coffi007https://github.com/Coffi007, thanks for reaching out to us. We will need more information to help you with this. Step 1: Can you please confirm if deployment was successful? You can validate this by navigating to, Resource Group > Overview > Deployment

Step 2: If deployment is successful, validate if authentication setup is configured correctly. Step 3 from Deployment Guidehttps://github.com/OfficeDev/microsoft-teams-emergency-operations-center/wiki/Deployment-Guide#3-set-up-authentication. Resource Group > App Service > Configuration

Can you replicate the issue in the browser and share the console logs and network trace to me for troubleshoot on this issue?

— Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/microsoft-teams-emergency-operations-center/issues/134#issuecomment-1690911642, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BCDJVWWZLHXYXRGRYMSPCBDXW26U3ANCNFSM6AAAAAA34C6U2Y. You are receiving this because you were mentioned.Message ID: @.**@.>>

eocrlundprosimpleauth.azurewebsites.net/auth/token:1

    Failed to load resource: the server responded with a status of 401 (Unauthorized)

eocrlundprosimpleauth.azurewebsites.net/auth/token:1

    Failed to load resource: the server responded with a status of 401 (Unauthorized)

teamsUserCredential.browser.ts:508 Uncaught (in promise) n.InternalError: Failed to get access token with error: Request failed with status code 401 at e.value (teamsUserCredential.browser.ts:508:12) at teamsUserCredential.browser.ts:119:27 at p (regeneratorRuntime.js:44:17) at Generator. (regeneratorRuntime.js:125:22) at Generator.throw (regeneratorRuntime.js:69:21) at r (asyncToGenerator.js:3:20) at l (asyncToGenerator.js:25:9) InstrumentHooks.js:93

    POST https://eocrlundprosimpleauth.azurewebsites.net/auth/token 401 (Unauthorized)

(anonymous) @ InstrumentHooks.js:93 (anonymous) @ xhr.js:210 e.exports @ xhr.js:15 e.exports @ dispatchRequest.js:56 Promise.then (async) u.request @ Axios.js:88 r.forEach.u. @ Axios.js:140 (anonymous) @ bind.js:9 (anonymous) @ teamsUserCredential.browser.ts:229 p @ regeneratorRuntime.js:44 (anonymous) @ regeneratorRuntime.js:125 (anonymous) @ regeneratorRuntime.js:69 r @ asyncToGenerator.js:3 s @ asyncToGenerator.js:22 Promise.then (async) r @ asyncToGenerator.js:12 s @ asyncToGenerator.js:22 (anonymous) @ asyncToGenerator.js:27 (anonymous) @ asyncToGenerator.js:19 (anonymous) @ teamsUserCredential.browser.ts:256 (anonymous) @ teamsUserCredential.browser.ts:116 p @ regeneratorRuntime.js:44 (anonymous) @ regeneratorRuntime.js:125 (anonymous) @ regeneratorRuntime.js:69 r @ asyncToGenerator.js:3 s @ asyncToGenerator.js:22 (anonymous) @ asyncToGenerator.js:27 (anonymous) @ asyncToGenerator.js:19 (anonymous) @ teamsUserCredential.browser.ts:121 p @ MicrosoftTeams.min.js:1 t.callHandler @ MicrosoftTeams.min.js:1 g @ MicrosoftTeams.min.js:1 u @ MicrosoftTeams.min.js:1 l.messageListener @ MicrosoftTeams.min.js:1 postMessage (async) g @ statics.teams.cdn.of…osoftTeams.min.js:1 l @ statics.teams.cdn.of…osoftTeams.min.js:1 n.processMessage @ statics.teams.cdn.of…osoftTeams.min.js:1 t @ statics.teams.cdn.of…osoftTeams.min.js:1 postMessage (async) y @ MicrosoftTeams.min.js:1 g @ MicrosoftTeams.min.js:1 u @ MicrosoftTeams.min.js:1 l.messageListener @ MicrosoftTeams.min.js:1 postMessage (async) b @ statics.teams.cdn.of…osoftTeams.min.js:1 u @ statics.teams.cdn.of…osoftTeams.min.js:1 (anonymous) @ eocrlundpro.azureweb…et/auth-end.html:16 teamsUserCredential.browser.ts:508 Uncaught (in promise) n.InternalError: Failed to get access token with error: Request failed with status code 401 at e.value (teamsUserCredential.browser.ts:508:12) at teamsUserCredential.browser.ts:119:27 at p (regeneratorRuntime.js:44:17) at Generator. (regeneratorRuntime.js:125:22) at Generator.throw (regeneratorRuntime.js:69:21) at r (asyncToGenerator.js:3:20) at l (asyncToGenerator.js:25:9)

[v-asshrirao]

@Coffi007 , Can you please share manifest files with us to analyse this issue further. Also please refer issue #13 where user reported similar issue.

[Coffi007]

Here is the Manifest file.

From: v-asshrirao @.> Sent: Thursday, August 24, 2023 7:16 AM To: OfficeDev/microsoft-teams-emergency-operations-center @.> Cc: Rob Lundquist @.>; Mention @.> Subject: Re: [OfficeDev/microsoft-teams-emergency-operations-center] Unable to get past Login screen in Teams (Issue #134)

@Coffi007https://github.com/Coffi007 , Can you please share manifest files with us to analyse this issue further. Also please refer issue #13https://github.com/OfficeDev/microsoft-teams-emergency-operations-center/issues/13 where user reported similar issue.

— Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/microsoft-teams-emergency-operations-center/issues/134#issuecomment-1691770051, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BCDJVWRT7TO6GRVKENEJKK3XW5O3ZANCNFSM6AAAAAA34C6U2Y. You are receiving this because you were mentioned.Message ID: @.**@.>>

[Coffi007]

Her is the manifest from the app registration

From: v-asshrirao @.> Sent: Thursday, August 24, 2023 7:16 AM To: OfficeDev/microsoft-teams-emergency-operations-center @.> Cc: Rob Lundquist @.>; Mention @.> Subject: Re: [OfficeDev/microsoft-teams-emergency-operations-center] Unable to get past Login screen in Teams (Issue #134)

@Coffi007https://github.com/Coffi007 , Can you please share manifest files with us to analyse this issue further. Also please refer issue #13https://github.com/OfficeDev/microsoft-teams-emergency-operations-center/issues/13 where user reported similar issue.

— Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/microsoft-teams-emergency-operations-center/issues/134#issuecomment-1691770051, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BCDJVWRT7TO6GRVKENEJKK3XW5O3ZANCNFSM6AAAAAA34C6U2Y. You are receiving this because you were mentioned.Message ID: @.**@.>>

[v-asshrirao]

@Coffi007, Can you please upload the file here in this issue ticket through GitHub rather than attaching it in email? I could not receive any links or attachments sent via email.

[Coffi007]

Error loading.docx Actually, the login issue is resolved not that I changed the access token value to 2.

Now I am logged in but the page is not loading. Here is a screen shot of the console code error. @.***

From: v-asshrirao @.> Sent: Thursday, August 24, 2023 7:44 AM To: OfficeDev/microsoft-teams-emergency-operations-center @.> Cc: Rob Lundquist @.>; Mention @.> Subject: Re: [OfficeDev/microsoft-teams-emergency-operations-center] Unable to get past Login screen in Teams (Issue #134)

@Coffi007https://github.com/Coffi007, Can you please upload the file here in this issue ticket through GitHub rather than attaching it in email? I could not receive any links or attachments sent via email.

— Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/microsoft-teams-emergency-operations-center/issues/134#issuecomment-1691822025, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BCDJVWT7RVISABKLOR5WRTTXW5SETANCNFSM6AAAAAA34C6U2Y. You are receiving this because you were mentioned.Message ID: @.***>

[v-asshrirao]

@Coffi007, I believe you have provisioned the SharePoint site for TEOC before deploying the solution in Azure. If yes, can you please check the REACT_APP_SHAREPOINT_SITE_NAME configuration in your app service ? (In Azure portal, navigate to TEOC resource group, open app service and click on Configuration)

It should be just the site name, if you have provided the full URL of the site by any chance, please update that to sitename as shown above and click ok and Save it.

Then perform this step, to get the code updated with the new site name value in your app service. Once that is done, open the app in teams and verify if that works as expected.

[Coffi007]

This is configured properly .

sharepointnaming.docx

[Coffi007]

Here is the latest log file teams.microsoft.com-1692900430469.log

[v-asshrirao]

@Coffi007, Everything looks correct. Can you please perform this step and confirm if its working?

[microsoft-github-policy-service[bot]]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.