@microsoft/teamsfx-core 1.8.0 → 1.8.1-alpha.324752dff.0

package/templates/bicep/azureWebApp.provision.orchestration.bicep

@@ -0,0 +1,18 @@
+// Resources web app
+module azureWebAppProvision './provision/azureWebApp.bicep' = {
+  name: 'azureWebAppProvision'
+  params: {
+    provisionParameters: provisionParameters
+  }
+}
+
+
+output azureWebAppOutput object = {
+  teamsFxPluginId: 'azure-web-app'
+  sku: azureWebAppProvision.outputs.sku
+  appName: azureWebAppProvision.outputs.appName
+  domain: azureWebAppProvision.outputs.domain
+  appServicePlanName: azureWebAppProvision.outputs.appServicePlanName
+  resourceId: azureWebAppProvision.outputs.resourceId
+  endpoint: azureWebAppProvision.outputs.endpoint
+}

package/templates/bicep/botService.config.module.bicep

@@ -0,0 +1,33 @@
+@secure()
+param provisionParameters object
+param provisionOutputs object
+var resourceBaseName = provisionParameters.resourceBaseName
+var botAadAppClientId = provisionParameters['botAadAppClientId'] // Read AAD app client id for Azure Bot Service from parameters
+var botServiceName = contains(provisionParameters, 'botServiceName') ? provisionParameters['botServiceName'] : '${resourceBaseName}' // Try to read name for Azure Bot Service from parameters
+var botServiceSku = contains(provisionParameters, 'botServiceSku') ? provisionParameters['botServiceSku'] : 'F0' // Try to read SKU for Azure Bot Service from parameters
+var botDisplayName = contains(provisionParameters, 'botDisplayName') ? provisionParameters['botDisplayName'] : '${resourceBaseName}' // Try to read display name for Azure Bot Service from parameters
+
+// Register your web service as a bot with the Bot Framework
+resource azureBot 'Microsoft.BotService/botServices@2021-03-01' = {
+  kind: 'azurebot'
+  location: 'global'
+  name: botServiceName
+  properties: {
+    displayName: botDisplayName
+    endpoint: uri({{endpointVarName}} , '/api/messages')
+    msaAppId: botAadAppClientId
+  }
+  sku: {
+    name: botServiceSku // You can follow https://aka.ms/teamsfx-bicep-add-param-tutorial to add botServiceSku property to provisionParameters to override the default value "F0".
+  }
+}
+
+// Connect the bot service to Microsoft Teams
+resource botServiceMsTeamsChannel 'Microsoft.BotService/botServices/channels@2021-03-01' = {
+  parent: azureBot
+  location: 'global'
+  name: 'MsTeamsChannel'
+  properties: {
+    channelName: 'MsTeamsChannel'
+  }
+}

package/templates/bicep/botService.config.orchestration.bicep

@@ -0,0 +1,8 @@
+// Merge TeamsFx configurations to Bot service
+module teamsFxBotServiceConfig './teamsFx/botService.bicep' = {
+  name: 'teamsFxBotServiceConfig'
+  params: {
+    provisionParameters: provisionParameters
+    provisionOutputs: provisionOutputs
+  }
+}

package/templates/bicep/config.bicep

@@ -0,0 +1,3 @@
+@secure()
+param provisionParameters object
+param provisionOutputs object

package/templates/bicep/main.bicep

@@ -0,0 +1,18 @@
+@secure()
+param provisionParameters object
+
+module provision './provision.bicep' = {
+  name: 'provisionResources'
+  params: {
+    provisionParameters: provisionParameters
+  }
+}
+output provisionOutput object = provision
+module config './config.bicep' = {
+  name: 'config'
+  params: {
+    provisionParameters: provisionParameters
+    provisionOutputs: provision
+  }
+}
+output configOutput object = contains(reference(resourceId('Microsoft.Resources/deployments', config.name), '2020-06-01'), 'outputs') ? config : {}

package/templates/bicep/provision.bicep

@@ -0,0 +1,2 @@
+@secure()
+param provisionParameters object

package/templates/core/README.md

@@ -7,9 +7,9 @@ Embed existing web app is to bring your own static webpages and embed in Microso
 Before run this app locally, make sure you have prepared the following prerequisites:
 * An [M365 account for development](https://docs.microsoft.com/microsoftteams/platform/toolkit/accounts).
 
-Also, make sure your own static webpages meets the [prerequisites](https://aka.ms/teamsfx-existing-tab#prerequisites) and launches locally.
+Also, make sure your own static webpages meets the [prerequisites](https://aka.ms/teamsfx-embed-existing-web#prerequisites) and launches locally.
 
-Then, you can quickly start local preview via the environment tree view in Teams Toolkit, refer [Preview your Teams app](https://aka.ms/teamsfx-existing-tab#preview-your-teams-app) for more information.
+Then, you can quickly start local preview via the environment tree view in Teams Toolkit, refer [Preview your Teams app](https://aka.ms/teamsfx-embed-existing-web#preview-your-teams-app) for more information.
 
 ## Develop
 
@@ -34,13 +34,13 @@ The file contains template arguments with `{...}` statements which will be repla
 
 Teams Toolkit can help provision new Teams app per different environments.
 
-After provisioned, you can preview your app via the environment tree view in Teams Toolkit, refer [Preview your Teams app](https://aka.ms/teamsfx-existing-tab#preview-your-teams-app) for more information.
+After provisioned, you can preview your app via the environment tree view in Teams Toolkit, refer [Preview your Teams app](https://aka.ms/teamsfx-embed-existing-web#preview-your-teams-app) for more information.
 
 After finish development and to distribute your app to others, you can [Publish Teams apps using Teams Toolkit](https://docs.microsoft.com/microsoftteams/platform/toolkit/publish).
 
 ## Reference
 
-* [Embed Existing Web App with Teams Toolkit](https://aka.ms/teamsfx-existing-tab)
+* [Embed Existing Web App with Teams Toolkit](https://aka.ms/teamsfx-embed-existing-web)
 * [Teams Toolkit and Step-by-step Documentations](https://docs.microsoft.com/microsoftteams/platform/toolkit/teams-toolkit-fundamentals)
 * [Teams Toolkit CLI](https://docs.microsoft.com/microsoftteams/platform/toolkit/teamsfx-cli)
 * [Teams Toolkit Samples](https://github.com/OfficeDev/TeamsFx-Samples)

package/templates/plugins/resource/aad/auth/bot/README.md

@@ -1,17 +1,220 @@
-## How to enable SSO in TeamsFx Bot projects
+# Enable single sign-on for bot applications
 
-This doc will show you how to add Single sign-on (SSO) feature to TeamsFx Bot projects. Note that this article is only for Teams Toolkit Visual Studio Code Extension version after x.x.x or TeamsFx CLI version after x.x.x.
+Microsoft Teams provides a mechanism by which an application can obtain the signed-in Teams user token to access Microsoft Graph (and other APIs). Teams Toolkit facilitates this interaction by abstracting some of the Azure Active Directory (AAD) flows and integrations behind some simple, high level APIs. This enables you to add single sign-on (SSO) features easily to your Teams application.
 
-*Note: This article is only for bot hosted on Azure App Service. Bot that hosted on Azure Function is not supported now.*
+For a bot application, SSO manifests as an Adaptive Card which the user can interact with to invoke the AAD consent flow.
 
-*Note: This article is only for TeamsFx projects by Javascript and Typescript. For Dotnet, please refer to ${help link}.*
+# Changes to your project
 
-For more detail about SSO, please refer to the [wiki](https://aka.ms/teamsfx-add-sso-readme).
+When you added the SSO feature to your application, Teams Toolkit updated your project to support SSO:
 
-### What we have done in 'Add SSO' command
+After you successfully added SSO into your project, Teams Toolkit will create and modify some files that helps you implement SSO feature.
 
-By triggering `Add SSO` command, we will help you to setup your project to enable SSO and create `auth/bot` folder with some code snippet. For detail, please refer to the [wiki](https://aka.ms/teamsfx-add-sso-readme).
+| Action | File | Description |
+| - | - | - |
+| Create| `aad.template.json` under `templates/appPackage` | The Azure Active Directory application manifest that is used to register the application with AAD. |
+| Modify | `manifest.template.json` under `templates/appPackage` | An `webApplicationInfo` object will be added into your Teams app manifest template. This field is required by Teams when enabling SSO. |
+| Create | `auth/bot` | Reference code, redirect pages and a `README.md` file. These files are provided for reference. See below for more information. |
 
-### What you need to do after triggering 'Add SSO' command
+# Update your code to add SSO
 
-Please follow the [wiki](https://aka.ms/teamsfx-add-sso-readme) to update your source code, provision Azure AD app and deploy latest code.
+As described above, the Teams Toolkit generated some configuration to set up your application for SSO, but you need to update your application business logic to take advantage of the SSO feature as appropriate.
+
+## Set up the AAD redirects
+
+1. Move the `auth/bot/public` folder to `bot/src`. This folder contains HTML pages that the bot application hosts. When single sign-on flows are initiated with AAD, AAD will redirect the user to these pages.
+2. Modify your `bot/src/index.ts` to add the appropriate `restify` routes to these pages.
+
+## Update your business logic
+
+The sample business logic provides a function `showUserInfo` that requires an AAD token to call Microsoft Graph. This token is obtained by using the logged-in Teams user token. The flow is brought together in a dialog that will display a consent dialog if required; otherwise it will go straight to `showUserInfo`.
+
+To make this work in your application:
+
+1. Move `auth/bot/public` folder to `bot/src`.
+These folder contains HTML pages used for auth redirect, please note that you need to modify `bot/src/index` file to add routing to these pages.
+
+1. Move `auth/bot/sso` folder to `bot/src`.
+These folder contains three files as reference for sso implementation:
+    * `showUserInfo`: This implements a function to get user info with SSO token. You can follow this method and create your own method that requires SSO token.
+    * `ssoDialog`: This creates a [ComponentDialog](https://docs.microsoft.com/en-us/javascript/api/botbuilder-dialogs/componentdialog?view=botbuilder-ts-latest) that used for SSO.
+    * `teamsSsoBot`: This create a [TeamsActivityHandler](https://docs.microsoft.com/en-us/javascript/api/botbuilder/teamsactivityhandler?view=botbuilder-ts-latest) with `ssoDialog` and add `showUserInfo` as a command that can be triggered. 
+
+1. (Optional) Follow the code sample and register your own command with `addCommand` in this file.
+1. Execute the following commands under `bot/`: `npm install isomorphic-fetch`
+1. Execute the following commands under `bot/`: `npm install copyfiles` and replace following line in package.json:
+    ```
+    "tsc --build && shx cp -r ./src/adaptiveCards ./lib/src",
+    ```
+    with:
+    ```
+    "tsc --build && shx cp -r ./src/adaptiveCards ./lib/src && copyfiles src/public/*.html lib/",
+    ```
+    By doing this, the HTML pages used for auth redirect will be copied when building this bot project.
+
+1. After adding the following files, you need to create a new `teamsSsoBot` instance in `bot/src/index` file. 
+Please replace the following code:
+    ```
+    // Process Teams activity with Bot Framework.
+    server.post("/api/messages", async (req, res) => {
+        await commandBot.requestHandler(req, res);
+    });
+    ```
+
+    with:
+
+    ```
+    const handler = new TeamsSsoBot();
+    // Process Teams activity with Bot Framework.
+    server.post("/api/messages", async (req, res) => {
+        await commandBot.requestHandler(req, res, async (context)=> {
+            await handler.run(context);
+        });
+    });
+    ```
+
+1. Add routing in `bot/src/index` file as below:
+
+    ```
+    server.get(
+        "/auth-*.html",
+        restify.plugins.serveStatic({
+            directory: path.join(__dirname, "public"),
+        })
+    );
+    ```
+
+1. Add the following lines to `bot/src/index` to import `teamsSsoBot` and `path`:
+
+    ```
+    // For ts:
+    import { TeamsSsoBot } from "./sso/teamsSsoBot";
+    const path = require("path");
+
+    // For js:
+    const { TeamsSsoBot } = require("./sso/teamsSsoBot");
+    const path = require("path");
+    ```
+
+1. Register your command in the Teams app manifest. Open `templates/appPackage/manifest.template.json`, and add following lines under `command` in `commandLists` of your bot:
+
+    ```
+    {
+        "title": "show",
+        "description": "Show user profile using Single Sign On feature"
+    }
+    ```
+
+## (Optional) Add a new command to the bot
+
+After successfully add SSO in your project, you can also add a new command.
+
+1. Create a new file (e.g. `todo.ts` or `todo.js`) under `bot/src/` and add your own business logic to call Graph API:
+
+    ```TypeScript
+    // for TypeScript:
+    export async function showUserImage(
+        context: TurnContext,
+        ssoToken: string,
+        param: any[]
+    ): Promise<DialogTurnResult> {
+        await context.sendActivity("Retrieving user photo from Microsoft Graph ...");
+
+        // Init TeamsFx instance with SSO token
+        const teamsfx = new TeamsFx().setSsoToken(ssoToken);
+
+        // Update scope here. For example: Mail.Read, etc.
+        const graphClient = createMicrosoftGraphClient(teamsfx, param[0]);
+        
+        // You can add following code to get your photo:
+        // let photoUrl = "";
+        // try {
+        //   const photo = await graphClient.api("/me/photo/$value").get();
+        //   photoUrl = URL.createObjectURL(photo);
+        // } catch {
+        //   // Could not fetch photo from user's profile, return empty string as placeholder.
+        // }
+        // if (photoUrl) {
+        //   await context.sendActivity(
+        //     `You can find your photo here: ${photoUrl}`
+        //   );
+        // } else {
+        //   await context.sendActivity("Could not retrieve your photo from Microsoft Graph. Please make sure you have uploaded your photo.");
+        // }
+
+        return;
+    }
+    ```
+
+    ```javascript
+    // for JavaScript:
+    export async function showUserImage(context, ssoToken, param) {
+        await context.sendActivity("Retrieving user photo from Microsoft Graph ...");
+    
+        // Init TeamsFx instance with SSO token
+        const teamsfx = new TeamsFx().setSsoToken(ssoToken);
+    
+        // Update scope here. For example: Mail.Read, etc.
+        const graphClient = createMicrosoftGraphClient(teamsfx, param[0]);
+        
+        // You can add following code to get your photo:
+        // let photoUrl = "";
+        // try {
+        //   const photo = await graphClient.api("/me/photo/$value").get();
+        //   photoUrl = URL.createObjectURL(photo);
+        // } catch {
+        //   // Could not fetch photo from user's profile, return empty string as placeholder.
+        // }
+        // if (photoUrl) {
+        //   await context.sendActivity(
+        //     `You can find your photo here: ${photoUrl}`
+        //   );
+        // } else {
+        //   await context.sendActivity("Could not retrieve your photo from Microsoft Graph. Please make sure you have uploaded your photo.");
+        // }
+    
+        return;
+    }
+    ```
+
+1. Register a new command using `addCommand` in `teamsSsoBot`:
+
+    Find the following line:
+
+    ```
+    this.dialog.addCommand("ShowUserProfile", "show", showUserInfo);
+    ```
+
+    and add following lines after the above line to register a new command `photo` and hook up with method `showUserImage` added above:
+
+    ```
+    // As shown here, you can add your own parameter into the `showUserImage` method
+    // You can also use regular expression for the command here
+    const scope = ["User.Read"];
+    this.dialog.addCommand("ShowUserPhoto", new RegExp("photo\s*.*"), showUserImage, scope);
+    ```
+
+1. Register your command in the Teams app manifest. Open 'templates/appPackage/manifest.template.json', and add following lines under `command` in `commandLists` of your bot:
+
+    ```
+    {
+        "title": "photo",
+        "description": "Show user photo using Single Sign On feature"
+    }
+    ```
+
+# Debug your application
+
+You can debug your application by pressing F5.
+
+Teams Toolkit will use the AAD manifest file to register a AAD application registered for SSO.
+
+To learn more about Teams Toolkit local debug functionalities, refer to this [document](https://docs.microsoft.com/microsoftteams/platform/toolkit/debug-local).
+
+# Customize AAD applications
+
+The AAD [manifest](https://docs.microsoft.com/azure/active-directory/develop/reference-app-manifest) allows you to customize various aspects of your application registration. You can update the manifest as needed.
+
+Follow this [document](https://aka.ms/teamsfx-aad-manifest#customize-aad-manifest-template) if you need to include additional API permissions to access your desired APIs.
+
+Follow this [document](https://aka.ms/teamsfx-aad-manifest#How-to-view-the-AAD-app-on-the-Azure-portal) to view your AAD application in Azure Portal.

package/templates/plugins/resource/aad/auth/bot/js/public/auth-end.html

@@ -1,3 +1,6 @@
+<!--This file is auto generated by Teams Toolkit to provide you instructions and reference code to implement single sign on. -->
+<!--This file is used during the Teams Bot authentication flow to assist with retrieval of the access token.-->
+<!--If you're not familiar with this, do not alter or remove this file from your project.-->
 <html>
   <head>
     <title>Login End Page</title>
@@ -34,7 +37,7 @@
 
       // Parse hash parameters into key-value pairs
       function getHashParameters() {
-        let hashParams = {};
+        let hashParams = new Map();
         location.hash
           .substr(1)
           .split("&")

package/templates/plugins/resource/aad/auth/bot/js/public/auth-start.html

@@ -1,3 +1,4 @@
+<!--This file is auto generated by Teams Toolkit to provide you instructions and reference code to implement single sign on. -->
 <!--This file is used during the Teams Bot authentication flow to assist with retrieval of the access token.-->
 <!--If you're not familiar with this, do not alter or remove this file from your project.-->
 <html>

package/templates/plugins/resource/aad/auth/bot/js/sso/showUserInfo.js

@@ -1,11 +1,24 @@
-import { createMicrosoftGraphClient, TeamsFx } from "@microsoft/teamsfx";
+// This file is auto generated by Teams Toolkit to provide you instructions and reference code to implement single sign on.
+// This file implements a function to call Graph API with TeamsFx SDK to get user profile with SSO token.
+// You can modify this file to add your business with SSO token.
+// See https://aka.ms/teamsfx-add-sso to learn more about adding new command to your bot.
 
-export async function showUserInfo(context, ssoToken) {
+const { createMicrosoftGraphClient, TeamsFx } = require("@microsoft/teamsfx");
+
+// If you need extra parameters, you can add param in `addCommand`
+async function showUserInfo(context, ssoToken, param) {
   await context.sendActivity("Retrieving user information from Microsoft Graph ...");
+
+  // Init TeamsFx instance with SSO token
   const teamsfx = new TeamsFx().setSsoToken(ssoToken);
+
+  // Add scope for your Azure AD app. For example: Mail.Read, etc.
   const graphClient = createMicrosoftGraphClient(teamsfx, ["User.Read"]);
+
+  // Call graph api use `graph` instance to get user profile information
   const me = await graphClient.api("/me").get();
   if (me) {
+    // Bot will send the user profile info to user
     await context.sendActivity(
       `You're logged in as ${me.displayName} (${me.userPrincipalName})${
         me.jobTitle ? `; your job title is: ${me.jobTitle}` : ""
@@ -17,3 +30,7 @@ export async function showUserInfo(context, ssoToken) {
 
   return;
 }
+
+module.exports = {
+  showUserInfo,
+};

package/templates/plugins/resource/aad/auth/bot/js/sso/ssoDialog.js

@@ -1,20 +1,25 @@
-import {
+// This file is auto generated by Teams Toolkit to provide you instructions and reference code to implement single sign on.
+// This file implements a `ComponentDialog` class for Single Sign On.
+// See https://docs.microsoft.com/javascript/api/botbuilder-dialogs/componentdialog?view=botbuilder-ts-latest for more about `ComponentDialog`.
+// If you are not familiar with this, do not remove or update this file.
+
+const {
   ComponentDialog,
   WaterfallDialog,
   Dialog,
   DialogTurnResult,
   DialogSet,
   DialogTurnStatus,
-} from "botbuilder-dialogs";
-import { ActivityTypes, tokenExchangeOperationName, TurnContext } from "botbuilder";
-import { TeamsBotSsoPrompt, TeamsFx } from "@microsoft/teamsfx";
-import "isomorphic-fetch";
+} = require("botbuilder-dialogs");
+const { ActivityTypes, tokenExchangeOperationName, TurnContext } = require("botbuilder");
+const { TeamsBotSsoPrompt, TeamsFx } = require("@microsoft/teamsfx");
+require("isomorphic-fetch");
 
 const DIALOG_NAME = "SSODialog";
 const TEAMS_SSO_PROMPT_ID = "TeamsFxSsoPrompt";
 const COMMAND_ROUTE_DIALOG = "CommandRouteDialog";
 
-export class SsoDialog extends ComponentDialog {
+class SsoDialog extends ComponentDialog {
   constructor(dedupStorage, requiredScopes) {
     super(DIALOG_NAME);
 
@@ -23,6 +28,7 @@ export class SsoDialog extends ComponentDialog {
     this.dedupStorage = dedupStorage;
     this.dedupStorageKeys = [];
     this.requiredScopes = requiredScopes;
+    this.commandMapping = new Map();
 
     const teamsFx = new TeamsFx();
     const ssoDialog = new TeamsBotSsoPrompt(teamsFx, TEAMS_SSO_PROMPT_ID, {
@@ -37,19 +43,25 @@ export class SsoDialog extends ComponentDialog {
     this.addDialog(commandRouteDialog);
   }
 
-  addCommand(commandId, commandText, operation) {
+  addCommand(commandId, commandText, operation, ...param) {
     const dialog = new WaterfallDialog(commandId, [
       this.ssoStep.bind(this),
       this.dedupStep.bind(this),
       async (stepContext) => {
         const tokenResponse = stepContext.result;
         const context = stepContext.context;
-        if (tokenResponse) {
-          await operation(context, tokenResponse.ssoToken);
-        } else {
+        try {
+          if (tokenResponse) {
+            await operation(context, tokenResponse.ssoToken, param);
+          } else {
+            await context.sendActivity("Failed to retrieve user token from conversation context.");
+          }
+          return await stepContext.endDialog();
+        } catch (error) {
           await context.sendActivity("Failed to retrieve user token from conversation context.");
+          await context.sendActivity(error.message);
+          return await stepContext.endDialog();
         }
-        return await stepContext.endDialog();
       },
     ]);
 
@@ -94,16 +106,30 @@ export class SsoDialog extends ComponentDialog {
   }
 
   async ssoStep(stepContext) {
-    return await stepContext.beginDialog(TEAMS_SSO_PROMPT_ID);
+    try {
+      return await stepContext.beginDialog(TEAMS_SSO_PROMPT_ID);
+    } catch (error) {
+      const context = stepContext.context;
+      await context.sendActivity("Failed to run SSO step");
+      await context.sendActivity(error.message);
+      return await stepContext.endDialog();
+    }
   }
 
   async dedupStep(stepContext) {
-    const tokenResponse = stepContext.result;
-    // Only dedup after ssoStep to make sure that all Teams client would receive the login request
-    if (tokenResponse && (await this.shouldDedup(stepContext.context))) {
-      return Dialog.EndOfTurn;
+    try {
+      const tokenResponse = stepContext.result;
+      // Only dedup after ssoStep to make sure that all Teams client would receive the login request
+      if (tokenResponse && (await this.shouldDedup(stepContext.context))) {
+        return Dialog.EndOfTurn;
+      }
+      return await stepContext.next(tokenResponse);
+    } catch (error) {
+      const context = stepContext.context;
+      await context.sendActivity("Failed to run dedup step");
+      await context.sendActivity(error.message);
+      return await stepContext.endDialog();
     }
-    return await stepContext.next(tokenResponse);
   }
 
   async onEndDialog(context) {
@@ -156,7 +182,7 @@ export class SsoDialog extends ComponentDialog {
 
   matchCommands(text) {
     for (const command of this.commandMapping) {
-      let pattern = command[1];
+      const pattern = command[1];
       let matchResult;
       if (typeof pattern == "string") {
         matchResult = text === pattern;
@@ -171,3 +197,5 @@ export class SsoDialog extends ComponentDialog {
     return undefined;
   }
 }
+
+exports.SsoDialog = SsoDialog;

package/templates/plugins/resource/aad/auth/bot/js/sso/teamsSsoBot.js

@@ -1,8 +1,13 @@
-import { ConversationState, MemoryStorage, TeamsActivityHandler, UserState } from "botbuilder";
-import { showUserInfo } from "./showUserInfo";
-import { SsoDialog } from "./ssoDialog";
+// This file is auto generated by Teams Toolkit to provide you instructions and reference code to implement single sign on.
+// This file implements a `TeamsActivityHandler` class using `ssoDialog` and add `showUserInfo` as a command.
+// See https://docs.microsoft.com/javascript/api/botbuilder/teamsactivityhandler?view=botbuilder-ts-latest for more about `TeamsActivityHandler`.
+// You can add your own command that requires SSO in this file.
 
-export class TeamsSsoBot extends TeamsActivityHandler {
+const { ConversationState, MemoryStorage, TeamsActivityHandler, UserState } = require("botbuilder");
+const { showUserInfo } = require("./showUserInfo");
+const { SsoDialog } = require("./ssoDialog");
+
+class TeamsSsoBot extends TeamsActivityHandler {
   constructor() {
     super();
 
@@ -19,7 +24,8 @@ export class TeamsSsoBot extends TeamsActivityHandler {
 
     // Add commands that requires user authentication
     this.dialog.addCommand("ShowUserProfile", "show", showUserInfo);
-    // call the `addCommand` function to add more customized commands
+    // Call the `addCommand` function to add more customized commands with your own parameters, e.g.
+    // this.dialog.addCommand("ManageToDo", new RegExp("todo\s*.*"), todoCmdHandler, param);
 
     this.onMessage(async (context, next) => {
       console.log("Running with Message Activity.");
@@ -53,3 +59,5 @@ export class TeamsSsoBot extends TeamsActivityHandler {
     await this.dialog.run(context, this.dialogState);
   }
 }
+
+exports.TeamsSsoBot = TeamsSsoBot;