Botframework-solutions: Token exchange process starts but rise an InternalServerError exception.

Created on 14 Sep 2020  路  7Comments  路  Source: microsoft/botframework-solutions

The token exchange process starts but rise an InternalServerError exception (see attachment).

Exception on token exchange.txt

_Originally posted by @GitDruid in https://github.com/microsoft/botframework-solutions/issues/3579#issuecomment-663121663_

Bot Services customer-replied-to customer-reported

All 7 comments

@Batta32 Can you take a look at this?

Sure @tdurnford! We will be reviewing this issue and the PR #3655. As soon as we have any update, we will back here 馃槉.

Hi @GitDruid, we were able to reproduce the InternalServerError exception.

So far the changes made on the PR #3655 seems to be right regarding the botbuilder SDK and following the sample sso-with-skills, but we want to validate that it does fix the error.

As soon as we have any update, we will back to you 馃槉.

InternalServerError exception
image

@tdurnford & @GitDruid - after reviewing the changes of PR #3655, we confirmed that the changes are correct and follows the signature of the ExchangeTokenAsync of IExtendedUserTokenProvider for botbuilder-dotnet and the parameters had to be inverted. Also, in botbuilder-js the signature is the same and the sample sso-with-skills contains the same changes.

Last but not least, we did the following things apart from this Pull Request to have a consistency between TypeScript and C#:

  • PR #3667: which applies these changes to the C# Virtual Assistant Sample
  • Commit of PR #3584: which applies these changes in TypeScript for a parity with C#

Hi @GitDruid - we are finalizing a plan to release new packages that will include the PR #3655 and PR #3667. As soon as we have any update we will back to you 馃槉.

@batta32, @ryanlengel, @peterinnesmsft any updates on this issue or the associated PRs? #3655 #3667

Hi @stevengum, we created the PR #3686 that duplicates the changes of the PR #3655. As soon as it's merged, this issue will be closed.

Last but not least, the PR #3667 was already merged.

Was this page helpful?
0 / 5 - 0 ratings