Open catmanjan opened 1 year ago
Hi catmanjan! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.
Best regards, Teams Platform
From this doco I believe we shouldn't even be asked for sign in: https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/authentication/bot-sso-code?tabs=cs1%2Ccs2%2Ccs3%2Ccs4%2Ccs5&pivots=bot-app
Hi @catmanjan - If you are having SSO configured in your app then you need to configure these settings in your appsettings.json
file of your code.
"MicrosoftAppType": "MultiTenant", // Set this to SingleTenant if you are using a single tenant app registration
"MicrosoftAppTenantId": "common" // Set your tenantId here if you are using single tenant app registration.
@Prasad-MSFT yes we have these, we already have sso working in another tenant but this new tenant when I click sign in I get a JavaScript error above
@catmanjan - From the console error it is not quite clear what's the cause of the issue? Is it happening only with this tenant?
@Prasad-MSFT this is the first new tenant we have set up our integration in - how can I get more information for you to diagnose this issue? We see nothing in our own logs
@catmanjan - Is it possible for you to share the tenant id and app details, so that we can have a look at our end?
You can send a mail to microsoftteamsdev@microsoft.com
@Prasad-MSFT 5166d23c-0135-4648-aca2-25cb29d6c70f
@catmanjan - I mean to say, we need the tenant credentials and app details to login to the account and check the issue.
@Prasad-MSFT I've sent those through, to reproduce the issue go to Teams and type @Ingress Search in search bar and select enterprise search, try to sign in from there
@catmanjan - We tried to repro this issue using the credentials provided and observed the same behaviour.
We request to share the sample code you used, so that accordingly we can raise a bug for this.
@Prasad-MSFT I'll send our bot source code to that email, we don't have a sample code because this is a real app
@catmanjan - Thanks for sharing the source code. We have raised a bug for the same. We will inform you once we get any further update from engineering team.
@Prasad-MSFT any update?
@catmanjan - At the moment, we have not received any updates from the engineering team. However, we are actively communicating with them to stay updated on the progress. As soon as we receive any updates from them, we will notify you in this thread. Thank you!
@Prasad-MSFT @ChetanSharma-msft any update? This is a big blocker for us...
Apologies @catmanjan, we are actively communicating with engineering team to stay updated on the progress. We have also made them aware of the seriousness of the issue. As soon as we receive any updates from them, we will notify you in this thread.
Thank you!
@Prasad-MSFT can we get an update? This is a massive issue
@catmanjan - We are actively communicating with them to stay updated on the progress. We have also made them aware of the seriousness of the issue. As soon as we receive any updates from them, we will notify you in this thread. Thank you!
@Prasad-MSFT any update on this?
@catmanjan - Apologies. We have not received any updates from the engineering team. As soon as we receive any updates from them, we will notify you in this thread. Thank you!
@Prasad-MSFT its been months, how can we escalate this?
@catmanjan - Apologies. Currently there is no updates from the engineering team. We have increased the severity and escalated internally. We will inform you once we have further update. Thanks!
@Prasad-MSFT please can we get an update?
Apologies, till now we have not received any updates from the engineering team. We have also made them aware of the seriousness of the issue. As soon as we receive any updates from them, we will notify you in this thread.
Thank you!
Hi @catmanjan - Could you please let us know whether you are still able to repro this issue or not?
@Prasad-MSFT yes, 9 months later it still doesn't work
We have just set our Teams bot up in another tenant and they are getting this error when they try to do an SSO sign in - any ideas how to troubleshoot?
The bot is working fine in our tenant BTW