Azure Gov WebChat: DirectLine Enhanced Authentication resulted in magic number authentication

Screenshots

Bot channel registration directline settings

Load bot from trusted URL

OAuthPrompt card displayed in webchat

Error in F12 after clicking on the button

A new tab for magic code was opened

Version

4.7.1 through NPM

Describe the bug

v4.7.2 .NET Core Bot is hosted in Microsoft Azure Government (MAG). DirectLine Enhanced Authentication does not work in trusted urls and resulted in magic code authentication instead of the expected behavior (new tab open and close automatically without user having to do manual input). F12 on browser displayed the following error

GET https://directline.botframework.azure.us/v3/directline/session/getsessionid 500

The error

Steps to reproduce

1. Setup a sample auth bot in Azure MAG.

2. Use the following values in appsettings.json { "BotEnv": "usgovprd", "ChannelService": "https://botframework.azure.us", "MicrosoftAppId": "[Omited]", "MicrosoftAppPassword": "[Omitted]", "ScmType": "None", "isAzureGovernment": true, "OAuthConnectionName": "aadv2" }

3. Use the following codes before prompting the OAuthPrompt card. OAuthClientConfig.OAuthEndpoint = "https://token.botframework.azure.us"; MicrosoftAppCredentials.TrustServiceUrl("https://token.botframework.azure.us");

4. Configure directline channel on the bot channel registration. Enable Enhanced Authentication and add a trusted url.

5. Configure an OAuth authentication connection with AADV2 as provider. The service principal used is from a GCC tenant.

6. Get a token from https://directline.botframework.azure.us/v3/directline/tokens/generate with a user id ‘dl_[new guid]’

7. Add a webchat control to the home page of the trusted url with code similar to below

          let directLineConnection = window.WebChat.createDirectLine({
              token: accessToken,
              domain: 'https://directline.botframework.azure.us/v3/directline' 
          });
   
          .....
   
          window.WebChat.renderWebChat({
              directLine: directLineConnection,
              store,
              styleOptions
          }, document.getElementById('webchat'));
   

8. Go to the trusted url to launch the homepage and webchat.

9. Interact with the bot to get an OAuthPrompt card back.

10. Click on the OAuthPrompt card.

11. Magic code authentication screen is displayed instead of the expected behavior

Expected behavior

The OAuthPrompt card should open up a new browser tab, close it, and auth token is received automatically in webchat as on the Azure commercial side.

Note

The magic code can be used to successfully authenticate the user.

[AngryVirginian]

@p-nagpal I confirm that the issue has been resolved in both Arlington and Fairfax datacenters. Please proceed with closing the ticket. Thank you fort he quick responses.

[AngryVirginian]

@p-nagpal you are right. My mistake. I turned off Enhanced Authentication during testing. It is working in the Fairfax datacenter now. I will test the other us gov bot that is in the Arlington datacenter on Monday.