Closed markroloff closed 5 years ago
@markroloff Do you have your bot framework id/password defined in the backend configuration? PoshBot will use an SAS key to receive messages from Service Bus and the bot id/pwd to post messages back to Teams or to retrieve user information like it is trying to do in this case.
@devblackops I double-checked those last night and ran into the same issue. For the sake of my sanity, I'm going to take a scorched-earth approach and start it over from scratch just to make sure I didn't miss something silly. Will report back.
Interesting. Are you going to run through the docs end-to-end? I'd love to know if I missed a key step or if something is unclear.
You may also try and set this in your script:
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
This was fixed in https://github.com/poshbotio/PoshBot/issues/138
Sorry for the delay. Been swamped with work. Got it working this time around, so I must have fubared something along the way originally. I suspect it was with configuring the bot manifest in Teams.
However, after going through the steps more closely, I found that the function app's connection string name differs from what gets configured in the settings. I'll send a PR to you for that.
@markroloff how did you fix this issue? Im having the same problem.
Worked through the docs for setting up the Teams backend and have hit a roadblack. Bot appears to be receiving messages fine but fails to authenticate to Teams when attempting to convert the user id. Repeated in both private and public teams.
Expected Behavior
@poshbot !about
bot proceeds to tell me nice things about itself
Current Behavior
Shell output displays...
PoshBot.log shows...
Your Environment