Skip to content

Latest commit

 

History

History
 
 

46.teams-auth

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
bots
bots
 
 
deploymentTemplates
deploymentTemplates
 
 
dialogs
dialogs
 
 
teamsAppManifest
teamsAppManifest
 
 
.env
.env
 
 
.eslintrc.js
.eslintrc.js
 
 
README.md
README.md
 
 
index.js
index.js
 
 
package.json
package.json
 
 

README.md

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 building a bot for Teams.

At this stage the primary focus of this sample is how to use the Bot Framework support for oauth in your bot. The reason for prioritizing this is that 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 TeamsActivityHandler and implementing handleTeamsSigninVerifyState.

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 Azure AD (Azure Active Directory), GitHub, Uber, etc.

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.

See install-and-test-the-bot-in-teams

Prerequisites

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

  • Node.js version 10.14 or higher

    # determine node version
node --version

To try this sample

  • Clone the repository

    git clone https://github.com/Microsoft/botbuilder-samples.git

  • In a console, navigate to samples/javascript_nodejs/46.teams-auth

    cd samples/javascript_nodejs/46.teams-auth

  • Install modules

    npm install

  • Run ngrok - point to port 3978

    ngrok http -host-header=rewrite 3978

  • Create Bot Framework registration resource in Azure

  • Update the .env configuration for the bot to use the Microsoft App Id and App Password from the Bot Framework registration. (Note the App Password is referred to as the "client secret" in the azure portal and you can always create a new client secret anytime.)

  • This step is specific to Teams.

    • Edit the manifest.json contained in the teamsAppManifest 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 Microsoft App Id may occur multiple times in the manifest.json)
    • Zip up the contents of the teamsAppManifest folder to create a manifest.zip
    • Upload the manifest.zip to Teams (in the Apps view click "Upload a custom app")

  • Run the bot

    node index.js

Interacting with the bot in Teams

Note this manifest.json specified that the bot will be installed in a "personal" scope only. Please refer to Teams documentation for more details.

You can interact with this bot by sending it a message. The bot will respond by requesting you to login to AAD, then making a call to the Graph API on your behalf and returning the results.

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