nodejs

page_type	description	products	languages	extensions	urlFragment
sample	This sample app demonstrate iss how to use the Bot Framework support for oauth in your bot	office-teams office office-365	nodejs	contentType createdDate samples 28/02/2023 13:38:25 PM	officedev-microsoft-teams-samples-bot-teams-authentication-nodejs

Teams Auth Bot

Bot Framework v4 bot using Teams authentication

This bot has been created using Bot Framework, it shows how to get started with authentication in a bot for Microsoft Teams.

The focus of this sample is how to use the Bot Framework support for oauth in your bot. Teams behaves slightly differently than other channels in this regard. Specifically an Invoke Activity is sent to the bot rather than the Event Activity used by other channels. This Invoke Activity must be forwarded to the dialog if the OAuthPrompt is being used. This is done by subclassing the ActivityHandler and this sample includes a reusable TeamsActivityHandler. This class is a candidate for future inclusion in the Bot Framework SDK.

The sample uses the bot authentication capabilities in Azure Bot Service, providing features to make it easier to develop a bot that authenticates users to various identity providers such as Microsoft Entra ID, GitHub, Uber, etc. The OAuth token is then used to make basic Microsoft Graph queries.

IMPORTANT: The manifest file in this app adds "token.botframework.com" to the list of validDomains. This must be included in any bot that uses the Bot Framework OAuth flow.

• Interaction with the bot

Try it yourself - experience the App in your Microsoft Teams client

Please find below demo manifest which is deployed on Microsoft Azure and you can try it yourself by uploading the app package (.zip file link below) to your teams and/or as a personal app. (Sideloading must be enabled for your tenant, see steps here).

Teams Auth Bot: Manifest

Prerequisites

• Microsoft Teams is installed and you have an account (not a guest account)
• Node.js

   # determine node version
   node --version

• dev tunnel or ngrok latest version or equivalent tunnelling solution
• Teams Toolkit for VS Code or TeamsFx CLI

Run the app (Using Teams Toolkit for Visual Studio Code)

The simplest way to run this sample in Teams is to use Teams Toolkit for Visual Studio Code.

1. Ensure you have downloaded and installed Visual Studio Code
2. Install the Teams Toolkit extension
3. Select File > Open Folder in VS Code and choose this samples directory from the repo
4. Using the extension, sign in with your Microsoft 365 account where you have permissions to upload custom apps
5. Select Debug > Start Debugging or F5 to run the app in a Teams web client.
6. In the browser that launches, select the Add button to install the app to Teams.

If you do not have permission to upload custom apps (sideloading), Teams Toolkit will recommend creating and using a Microsoft 365 Developer Program account - a free program to get your own dev environment sandbox that includes Teams.

Setup

Note these instructions are for running the sample on your local machine, the tunnelling solution is required because the Teams service needs to call into the bot.

Setup for Bot Auth

Refer to Bot SSO Setup document.

1. Setup NGROK

• Run ngrok - point to port 3978

  ngrok http 3978 --host-header="localhost:3978"

  Alternatively, you can also use the dev tunnels. Please follow Create and host a dev tunnel and host the tunnel with anonymous user access command as shown below:

  devtunnel host -p 3978 --allow-anonymous

2. Setup for code

   • Clone the repository

   git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git

• In a terminal, navigate to samples\bot-teams-authentication\nodejs folder

• Install modules

  npm install

• Modify the .env file in your project folder (or in Visual Studio Code) and fill in below details:

  1. <<YOUR-MICROSOFT-APP-TYPE>> (Allowed values are: MultiTenant(default), SingleTenant, UserAssignedMSI)
  2. <<YOUR-MICROSOFT-APP-ID>> - Generated from Step 1 (Application (client) ID)is the application app id
  3. <<YOUR-MICROSOFT-APP-PASSWORD>> - Generated from Step 6, also referred to as Client secret
  4. <<YOUR-MICROSOFT-APP-TENANT-ID>> - Generated from Step 1(Directory (tenant) ID) is the tenant id
  5. <<YOUR-CONNECTION-NAME>> - Generated from step 7.

• Run your app

  npm start

3. This step is specific to Teams.
   • Edit the manifest.json contained in the appManifest folder to replace your Microsoft App Id (that was created when you registered your bot earlier) everywhere you see the place holder string <<YOUR-MICROSOFT-APP-ID>> (depending on the scenario the MicrosoftAppId may occur multiple times in the manifest.json)
   • Edit the manifest.json for {{domain-name}} with base Url domain. E.g. if you are using ngrok it would be https://1234.ngrok-free.app then your domain-name will be 1234.ngrok-free.app and if you are using dev tunnels then your domain will be like: 12345.devtunnels.ms.
   • Zip up the contents of the appManifest folder to create a manifest.zip (Make sure that zip file does not contains any subfolder otherwise you will get error while uploading your .zip package)
   • Upload the manifest.zip to Teams (In Teams Apps/Manage your apps click "Upload an app". Browse to and Open the .zip file. At the next dialog, click the Add button.)
   • Add the app to personal scope or 1:1 chat (Supported scope)

Note:

• If you are facing any issue in your app, please uncomment this line and put your debugger for local debug.

Running the sample

Install app:

Welcome to teamsbot:

Login UI: Authentication success:

Authentication token:

Logout UI:

Deploy the bot to Azure

To learn more about deploying a bot to Azure, see Deploy your bot to Azure for a complete list of deployment instructions.

Further reading

• Bot Framework Documentation
• Bot Basics
• Azure Bot Service Introduction
• Azure Bot Service Documentation
• Bot Authentication Basics