SOLVED

SSO fails at Invoke signin/verifyState

New Contributor

Following scenario: I have a working bot with an AAD v2 OAuth connection. Now i have created a new bot which is just for staging (DEV/PROD). This new bot works the same with one exception: SSO in MS Teams. Magic Code authentication works in both MS Teams and Emulator. SSO only works in Emulator. The error is the following:

 

Invoke failed due to internal error: Invoke failed: something went wrong in ProcessInvoke

 

This error occures when MS Teams sends the signin/verifyState Invoke Message to https://emea.ng.msg.teams.microsoft.com/v1/agents and results in a HTTP 500...

Since the SSO directly to my new bot does work in the Bot Framework Emulator i am sure this problem is on the site https://emea.ng.msg.teams.microsoft.com.

 

Both bots are configured in the same way. The only difference is the MS App ID and Password. This issue is a showbreaker for us, since we cannot use MS Teams if there is no SSO supported.

 

BR
David Vollmers

1 Reply
best response confirmed by dvolper (New Contributor)
Solution

UPDATE:

The Team around MS Teams seems to have fixed the issue. It is still not perfect but you can read about it here: https://github.com/MicrosoftDocs/msteams-docs/issues/718