[sso-with-skills] Authorizartion issues

[JFolberth]

Github issues for C# /JS / Java/ Python should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.

Sample information

1. Sample type: [\samples\experimental\sso-with-skills]
2. Sample language: [dotnetcore]
3. Sample name: SSO with Simple Skill Consumer and Skill

Describe the bug

Have a customer who is receiving "StatusCode": 401, "RawResponseBody": "{\"error\":{\"code\":\"InvalidAuthenticationToken\",\"message\":\"Access token validation failure. Invalid audience

I am walking through the repo and getting "Microsoft.Bot.Schema.ErrorResponseException: Operation returned an invalid status code Unauthorized at Microsoft.Bot.Connector.UserToken.GetTokenWithHttpMessagesAsync(String userId, String connectionName, String channelId, String code, Dictionary 2 customHeaders, CancellationToken cancellationToken) at Microsoft.Bot.Connector.UserTokenExtensions.GetTokenAsync(IUserToken operations, String userId, String connectionName, String channelId, String code, CancellationToken cancellationToken) at Microsoft.Bot.Builder.BotFrameworkAdapter.GetUserTokenAsync(ITurnContext turnContext, AppCredentials oAuthAppCredentials, String connectionName, String magicCode, CancellationToken cancellationToken) at Microsoft.Bot.Builder.Dialogs.UserTokenAccess.GetUserTokenAsync(ITurnContext turnContext, OAuthPromptSettings settings, String magicCode, CancellationToken cancellationToken) at Microsoft.Bot.Builder.Dialogs.OAuthPrompt.BeginDialogAsync(DialogContext dc, Object options, CancellationToken cancellationToken) at Microsoft.Bot.Builder.Dialogs.DialogContext.BeginDialogAsync(String dialogId, Object options, CancellationToken cancellationToken)

I have confirmed via curl locally that am able to retrieve the correct and valid token.

To Reproduce

Steps to reproduce the behavior:

1. Launch the code in the emulator after configuring the root and skill bot (Confirmed both are able to get an OAuth Connection)
2. Locally emulator connected to running instance of RootBot
3. Welcome message appears
4. Type 'login'

Expected behavior

Expected to prompted with AAD login screen

Additional context

Add any other context about the problem here.

[breakingram]

Hi @JFolberth, I'm investigating this issue.

[breakingram]

Hi @JFolberth,

I was not able to reproduce this issue after following the sso-with-skills readme and Add single sign-on to a bot documentation.

Tested in WebChat, and after typing login I received the token.

For the first login activity message, I received a card to sign in. After that, whenever I type login, I automatically receive the token without signing in every time.

@JFolberth, are you facing this issue only if using Emulator?

[JFolberth]

So, couple things realized on this. My initial issue was ultimately misreading configuration of the app secret between a managed bot and single/multi tenant. However; ran into some additional items/feedback.

• The walkthrough assumes you have ngrok already configure to run, there is no mention of this. If you do not the experience is silently different as you will get an "emulatedToken"
• I ran into that the Emulator does not support the latest version of ngrok and found an issue opened with that #2389

[breakingram]

Hi @JFolberth, were you able to get the SSO with skill working?

[breakingram]

Closing due to lack of activity. @JFolberth please re-open if needed.