botkit

This issue had nothing to do with botkit.

Needed to update connection driver version in mongo atlas dashboard.

Was Node.js 3.0 or later driver version. When I changed that to the Node.js 2.2.12 or later version, that connection string worked.

The Botium Botkit 4.x Connector is based on the Botium Generic HTTP/JSON Connector, so it is possible to fully customize the payload, including the user id.

By default, the message payload is composed of the message text and a unique generated user id:

With the latest Botium Botkit Connector support for quick replies (buttons) and file attachments has been added.

So, if your Botkit bot replies something like this:

botkit-middleware-watson examples like this one show how WatsonMiddleware can be configured:

Technically, this is an alternative solution (I think). In order to create Google Hangouts credentials a GSuite account is required, which I don't have. The Interface HangoutsAdapterOptions docs state the "Shared secret token [is] used" for validation and is found under the Configuration tab. As the fields are locked down, I can't test this.

However, the alternative is to use the built-in OAuth feature of the Bot Framework. I use this in my bot without a hitch. I did navigate to the Google Hangouts web site and it recognized me immediately. By using the OAuth login, a token is returned which you can use to pass into the Hangouts adapter.

I should add that the below implementation produces a sign-in magic code which some people don't like (it doesn't bother me). There may be a SSO option, but I haven't researched that.

First, you need to setup Google credentials which will provide you with a "Client id" and "Client secret". General instructions can be found here. Credentials can be created here. You can ignore any coding references as they aren't necessary (thanks to the BF OAuth feature).

From the Credentials Page, click on "Credentials" in the left menu. There are two areas you need to configure, once there: "OAuth consent screen" and "Credentials".

For OAuth consent screen, provide an app name. This doesn't need to match the associated requesting app and is just for reference when visiting the Credentials Page. Enter a support email, the scopes you will be using (email, profile, and openid). There may be other required scopes, but this worked for me when I visited the Hangouts web site. Lastly, enter in the Authorized Domains. The botframework.com domain is required. Others, if any, you will have to experiment with. Save and return to the Credentials Page.

Click the "Create Credentials" button and complete the form. Give your credentials a name (again, not referenced anywhere else for this project), enter any authorized origins, and enter https://token.botframework.com/.auth/web/redirect as the authorized redirect URI. Save the settings, copy the "Client id" and "Client secret" somewhere, and navigate to Azure and into your bot's settings page.

Here, you need to create your bot's OAuth connection. This is done in the Settings blade. At the bottom of the blade is the "OAuth Connection Settings" section. Click the "Add Setting" button to get started.

Once in, give your connection a name. This name will be referenced by your bot in the next step, so save the name somewhere. Then, select Google from the list of Service Providers and paste the "Client id" and "Client secret", that you saved earlier, into the respective fields. In "Scopes", you will want to enter the same scope values you selected in your Google credentials app ("email profile openid"). Be sure they are space-separated when you enter them.

Lastly, you will want to model your OAuth login off of sample 18.bot-authentication from the Botbuilder-Samples repo. This builds in the functionality you need for enabling a user to log in via your bot.

Add the connection name you assigned to your Google connection setting for your bot into a .env file as a variable, like this: connectionName=.

When setting up the OAuth prompt, you will pass this variable in:

Ok. The problem was the callback link on Facebook's App.

Since I have a verification token on my code, as you can see below, I was pointing the facebook callback URL to my ngrok link and the verification was working fine. But it looks like to debug on azure configurations you must use the callback link that azure provides to you. Something like "https://facebook.botframework.com/api..." that you can find under channels / facebook.

Once I set the facebook APP to use azure callback link everything is working fine.

I've solved this issue. I put wrong credentials in .env file so.

The url has changed in v4 - it is now /api/messages

For Botkit to work with the BotFramework, you only need a few items to be configured. Compare what you have with the below, note any differences, and make the appropriate changes. I have this simple setup working.

First, this is how you can locate your BotFramework appId & appPassword, if you don't know it.

Navigate to your Azure bot's resource group. On the left menu pane, select Deployments.

Then select the bot deployment and select Inputs in the menu pane. This will then list your appId and appPassword.

Place this code in your index.js file. Be sure to do the necessary npm installs.