Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need help in configuring channels in my bot which is not deployed in Azure #530

Open
rammanavalan opened this issue Mar 10, 2023 · 1 comment

Comments

@rammanavalan
Copy link

Team,

I have used Bot framework composer (Version: 2.1.2) dotnet to build my bot. So far, I have been deploying the bot in Azure and enabled all my channels (Teams, Skype, Slack, Webex, etc) in the Azure portal. However, I need to move away from Azure to my local deployment. So, I dockerized and started the bot in my local deployment. I was able to successfully connect Webex to my bot using the Bot.Builder.Community.Adapters.Webex. However, I need help in the following:

  1. Slack channel: I used the library Bot.Builder.Community.Adapters.Slack and these settings in appsettings.json: SlackBotToken, SlackClientSigningSecret and SlackVerificationToken. And, this worked. However, I am not comfortable with this because of the SlackBotToken whose scope is Workspace level only. So, I looked at this source and used SlackClientId, SlackClientSecret, SlackScopes and SlackRedirectUri. But this fails with the error: System.AggregateException: One or more errors occurred. (Missing Slack API credentials! Provide SlackClientId, SlackClientSecret, scopes and SlackRedirectUri as part of the SlackAdapter options. Any help on this?

  2. I could not find similar adapter libraries for Teams and Skype. So, how do configure my bot (local deployment) to be able to receive/send messages from/to Teams and Skype?

Thanks much in advance.

@RamkumarManavalan
Copy link

Team, any help on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants