sp-dev-fx-webparts/samples/react-bot-framework-sso/webpart
Hugo Bernier 052ec4f3db Fixed query labels without the sample tag 2021-11-21 00:14:21 -05:00
..
config fix doc 2020-12-16 11:38:21 +08:00
images V1.0 2020-11-06 17:34:51 +08:00
src V1.0 2020-11-06 17:34:51 +08:00
.editorconfig V1.0 2020-11-06 17:34:51 +08:00
.gitignore V1.0 2020-11-06 17:34:51 +08:00
.yo-rc.json V1.0 2020-11-06 17:34:51 +08:00
README.md Fixed query labels without the sample tag 2021-11-21 00:14:21 -05:00
gulpfile.js V1.0 2020-11-06 17:34:51 +08:00
package-lock.json V1.0 2020-11-06 17:34:51 +08:00
package.json V1.0 2020-11-06 17:34:51 +08:00
tsconfig.json V1.0 2020-11-06 17:34:51 +08:00
tslint.json V1.0 2020-11-06 17:34:51 +08:00

README.md

Microsoft Bot Framework Web Chat with SSO

Summary

An web parts sample that uses the botframework-webchat module to create a React component to render the Bot Framework v4 webchat component. This web parts sample is a single sign-on demo for on behalf of authentication using OAuth.

When dealing with personal data, please respect user privacy. Follow platform guidelines and post your privacy statement online.

Compatibility

SPFx 1.10.0 Node.js v10 Compatible with SharePoint Online Does not work with SharePoint 2019 Does not work with SharePoint 2016 (Feature Pack 2) Local Workbench Incompatible Hosted Workbench Compatible

Applies to

Prerequisites

You need to get familiar with the web parts web chat sample first as this sample is based on that sample.

You need to have this bot created and registered using the Microsoft Bot Framework and registered to use the Direct Line Channel, which will give you the token generation endpoint needed when adding this web parts to the page. For more information on creating a bot and registering the channel you can see the official web site at dev.botframework.com.

Minimal Path to Awesome

  • Clone this repository

  • Edit BotSignInToast.tsx file to set your AAD scope uri(scopeUri) with api://YOUR_APP_ID directly like api://123a45b6-789c-01de-f23g-h4ij5k67a8bc:

    return tokenProvider.getToken(scopeUri, true).then((token: string) => {
    
  • Add the following config to ./config/package-solution.json:

        "webApiPermissionRequests": [
    +     {
    +       "resource": "<YOUR_APP_ID>",
    +       "scope": "<YOUR_AAD_SCOPE_NAME>"
    +     }
        ],
    
  • Refer Connect to Azure AD-secured APIs to publish and approve permissions from admin site

  • In the command line run

    cd ../extension
    npm install
    gulp serve
    
  • Open online test page with user account: https://<YOUR_SITE>.sharepoint.com/_layouts/15/Workbench.aspx

  • Config bot endpoint
    Add the web part, set bot endpoint to https://YOUR_BOT.azurewebsites.net, refresh this page, then you can successfully connet bot with SharePoint.

Deploy

If you want to deploy it follow these steps

Features

This Web Part illustrates the following concepts on top of the SharePoint Framework:

  • Connecting and communicating with a bot built on the Microsoft Bot Framework using the Direct Line Channel
  • Validating Property Pane Settings
  • Office UI Fabric
  • React
  • Demo single sign-on for on behalf of authentication using OAuth

Help

We do not support samples, but we this community is always willing to help, and we want to improve these samples. We use GitHub to track issues, which makes it easy for community members to volunteer their time and help resolve issues.

If you're having issues building the solution, please run spfx doctor from within the solution folder to diagnose incompatibility issues with your environment.

You can try looking at issues related to this sample to see if anybody else is having the same issues.

You can also try looking at discussions related to this sample and see what the community is saying.

If you encounter any issues while using this sample, create a new issue.

For questions regarding this sample, create a new question.

Finally, if you have an idea for improvement, make a suggestion.

Disclaimer

THIS CODE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.