MS Teams SSO signin failure with resourcematch failed #193132
Replies: 2 comments
-
|
Thanks for posting in the GitHub Community, @tharuds! We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category, the Discussions category is solely related to conversations around the GitHub product Discussions. This question should be in the |
Beta Was this translation helpful? Give feedback.
-
|
The fact that Quickest diagnostic: paste the JWT you're trying to exchange into jwt.ms, copy the If you want to share the (redacted) aud claim and the manifest resource field, I can spot the mismatch directly. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Discussion Type
Question
Discussion Content
Hi team,
I'm trying to implement single sign on for a simple bot app built using Teams SDK and I keep getting a 200 response with a sign in failure.
I have checked the application ID URI, token exchange URL (in bot resource) and the manifest
webApplicationInfowhich matches the api://{azuread-client-id} going through the troubleshooting tips.When I try to sign in from teams client the resource match failed keeps happening even if the troubleshooting checklist looks fine.
The Entra app is configured to support multiple entra ID accounts while the Azure bot resource is single tenant. I have also tried changing the Azure AD app supporting account types yet keep getting the same issue. I'm testing the bot app using the sandbox account created from the admin tenant that I used to configure azure resources, which has a different tenant id (domain - 250rr3.onmicrosoft.com).
I have also checked the jwt generated when testing the oauth connection (https://token.botframework.com/api/oauth/TestConnectionCallback) configured for the Azure bot resource and it works fine with graph endpoints.
Would be great to know what could be missing or if it could be a cache issue or an issue from the bot framework.
TIA
Beta Was this translation helpful? Give feedback.
All reactions