Freigeben über

Managing secrets with .BOT files in Bot Framework v4

  • Artikel

This article is now hosted at https://martink.me/articles/managing-secrets-with-bot-files-in-bot-framework-v4

All blog articles will be hosted on https://martink.me going forward

Comments

  • Anonymous
    September 28, 2018
    Certainly appreciate your writing this up! I've been pretty aggressively consuming Azure services for the past year and was mystified by this "new" approach in V4. I've wound up extending the OOB BotConfiguration to use Azure KeyVault for the file & secret, so no sensitive data has to be persisted on disk or in version control (using Managed Service Identity). Hope to see that as a default in V5.
  • Anonymous
    October 10, 2018
    Nice article!The problem I see is that if I use the bot file I need to share the secret with all devs for them to be able to use the bot. Am I right, am I missing something?
    • Anonymous
      November 07, 2018
      Yes you do need to share the secret if you have multiple devs working on the same bot.
  • Anonymous
    November 14, 2018
    Great write up except for the error in the structure of the .env file. It should be as follows.botFilePath=yourbasicBot.botbotFileSecret=ukxxxxxxxxxxxxs=Your JSON format does not work.