Luis Bot -> Error: Response status code does not indicate success: 403 (Forbidden).

[cxbuilders]

When a new bot is created with Luis enabled, in the Emulator it throws an error:
Response status code does not indicate success: 403 (Forbidden).

Version

ffde16f

To Reproduce

Steps to reproduce the behavior:

1.Create new echo based bot
2. Switch to Luis and add trigger with intent and some utterances
3. Run provision script
4. Copy settings from script in Bot settings in Composer
5. Start Bot & Run emulator
6. Type something to see the error
4. See error

[luhan2017]

@cxbuilders , so you started a local runtime by a deployed config. could you check the generated folder of your bot?

We are using this pattern to load the luis config file:
luis.settings.{luis.environment}.{luis.authoringRegion}.json

could you check the generated folder of your bot and your settings to see whether they match.

[cxbuilders]

@luhan2017 This is a vanilla bot in the latest version. I created the bot, enabled luis, ran the provisioncomposer.js script, filled in the settings in the appsettings and that's it.

File looks ok:

[luhan2017]

@cxbuilders , Oh, I know why this happen, in the deployment process, we are assigning the authored luis resource to the prediction luis service, which binds the endpointKey. So you should missed this part. You can try the following:

1. Use the authoringKey as the endpointKey.
2. kick of a deployment to bind the endpointKey with the luis resource.

[cxbuilders]

@luhan2017 Not completely clear. Are you saying I missed something or this is a bug?

[luhan2017]

@cxbuilders I mean you missed the deployment step, you can't just do provision and use the settings to start a local bot, you missed a luis endpoint assignment process which is in the deployment process.

[cxbuilders]

@luhan2017 Yeah but the provisionComposer.js script is the deployment script, right? Which I did run as mentioned

[luhan2017]

@cxbuilders
No, you should do deployment like this:

1. Click Add new profile, paste your provision result in the publish Configuration

2. Click publish to selected profile, select OK, then you are kicking off a deployment.

[mudasar]

I am having a similar error. It was working fine a couple of days ago but now when trying to run the bot on local with Luis integration it is returning this strange error without any further help that which kind of authentication is failed.