OfficeDev / microsoft-teams-emergency-operations-center

The Microsoft Teams Emergency Operations Center (TEOC) solution template leverages the power of the Microsoft 365 platform to centralize incident response, information sharing and field communications using powerful services like Microsoft Lists, SharePoint and more.
MIT License
95 stars 40 forks source link

Unable to login to App #192

Closed idavis162 closed 6 months ago

idavis162 commented 7 months ago

The app has been deployed and added to the team, but when I hit the login button, a prompt that says "almost there" pops up, I then hit continue, and then nothing happens. Any help is appreciated. Thanks. image

v-ajaysahu commented 6 months ago

@idavis162 , Thank you for reporting this. Please open teams in browser, then open the app and share console logs and network trace which will help us troubleshoot the issue. Also request you to share the manifest files with us.

idavis162 commented 6 months ago

Teams Info.zip

v-ajaysahu commented 6 months ago

@idavis162 , Thank you for sharing the Logs. As per the Shared logs you are getting SSO token error. Manifest file which you have shared is from Azure App Registration, we need Manifest file where you generated TEOC App zip as per this link. Kindly verify the Client Id and Client Secret which you have added in Apps Manifest JSON file and in App Registration either it could be mismatched, or Permission is mismatched.

image

idavis162 commented 6 months ago

Manifest.txt

v-ajaysahu commented 6 months ago

@idavis162 , Thanks for sharing Manifest file. Client Id seems to be correct. Kindly confirm whether Client Secret which you've added while creating the app is correct or not. To do this kindly navigate to your resource group and then navigate to App Service which ends with simple Auth then click on Environment Variables there you can find Client Secret verify whether it is correct or not. Once confirmed, kindly let us know.

idavis162 commented 6 months ago

image So would I use this ID? or the client secret? And where would I input that value?

v-ajaysahu commented 6 months ago

@idavis162 , Please ensure that the Client ID and Client Secret correspond with the App Registration you have created as per the below link. https://github.com/OfficeDev/microsoft-teams-emergency-operations-center/wiki/Deployment-Guide#2-register-azure-ad-application

idavis162 commented 6 months ago

So I have the correct Client ID. Where do I need to update that to try and get it to work?

v-ajaysahu commented 6 months ago

@idavis162 , If your client ID is incorrect, you should delete the Resource Group and attempt the process again with the correct client ID value.

idavis162 commented 6 months ago

Just to confirm, the base resource name and app domain is the one ending in simpleauth correct? As in reference to step 4.

v-ajaysahu commented 6 months ago

@idavis162 , Yes, that is correct. That's the base resource name.

idavis162 commented 6 months ago

image

Which is the right app service to use for the app domain and the base resource name? I rebuilt the app but now when trying to add it, it won't allow me to add it to the team.

idavis162 commented 6 months ago

image This is all that pops up when trying to add the app to the team

v-ajaysahu commented 6 months ago

@idavis162 , First App service name which has the base resource name. Instead of adding to teams Channel, can you try to open the app directly and confirm here?

image

idavis162 commented 6 months ago

I have confirmed the client secret is showing the correct value under the simpleauth app service. I have also made sure the base resource name is the lbbdomeoc. But now when logging this is what the console shows

Uncaught (in promise) h.InternalError: Failed to get access token with error: Get SSO token failed with error: Error: 500011 - [2024-05-16 16:26:56Z]: AADSTS500011: The resource principal named api://lbbdomeoc.azurewebsites.net/"Hidden but is the client ID from step 2"/access_as_user was not found in the tenant named City of Lubbock. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant. Trace ID: 936a398f-5a20-43c4-b7d4-4fe6dab06400 Correlation ID: d1b007e2-60f7-442e-bb70-281582811da1 Timestamp: 2024-05-16 16:26:56Z - Correlation ID: d1b007e2-60f7-442e-bb70-281582811da1 - Trace ID: 936a398f-5a20-43c4-b7d4-4fe6dab06400

v-ajaysahu commented 6 months ago

@idavis162 , Please share your email address and your availability so that we can schedule a MS Teams Call to troubleshoot this issue.

idavis162 commented 6 months ago

I am free today from 1-5 CST or anytime Monday-Friday 9-5 CST My email is @.***

Get Outlook for iOShttps://aka.ms/o0ukef


From: v-ajaysahu @.> Sent: Friday, May 17, 2024 12:45:01 AM To: OfficeDev/microsoft-teams-emergency-operations-center @.> Cc: idavis162 @.>; Mention @.> Subject: Re: [OfficeDev/microsoft-teams-emergency-operations-center] Unable to login to App (Issue #192)

WARNING: This message was sent from outside the City of Lubbock's email system.

It could contain harmful attachments or links to harmful web pages.


@idavis162https://github.com/idavis162 , Please share your email address and your availability so that we can schedule a MS Teams Call to troubleshoot this issue.

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

v-ajaysahu commented 6 months ago

@idavis162 , Please share your email address through GitHub. You've shared the email address through email which will not be visible to us.

idavis162 commented 6 months ago

idavis@mylubbock.us

v-ajaysahu commented 6 months ago

@idavis162 , I have scheduled a meeting for the 21st of May at 9:30 AM CST to address the issue. I hope this proposed time is suitable for you.

idavis162 commented 6 months ago

Got it now. Thanks!

v-ajaysahu commented 6 months ago

@idavis162 , As your issue has been resolved, I am closing this request. Please feel free to comment if you require further assistance.