You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 17, 2024. It is now read-only.
Hi, I'm working on deploying this app, and seem to be running into some problems. I have the app deployed the azure, and added the manifest to the Teams instance. However, when tagging the bot in a channel, I get a popup asking me to sign in (screenshot below). Clicking "Sign In" leads to an error that I am having trouble debugging (also screenshot below).
What are the proper steps to debugging this? I'm guessing its an issue with Azure being configured correctly. I have OAuth added to the bot, and client Id and Secret from Badgr entered in the correct places. Thanks!
The text was updated successfully, but these errors were encountered:
Ensure that you have given the redirect URL mentioned in step 2 of the deployment guide correctly.
Apart from this while deployment of this bot make sure you have entered the below mentioned things correctly:
f. Superuser username: User need to provide issuer group owners user id (Owner account used in Step 1)
g. Superuser Password: User need to provide issuer group owners password (Owner account password used in Step 1).
For badgr Oauth settings you need to provide the client secret id and value provided by badgr team.
Hi, I'm working on deploying this app, and seem to be running into some problems. I have the app deployed the azure, and added the manifest to the Teams instance. However, when tagging the bot in a channel, I get a popup asking me to sign in (screenshot below). Clicking "Sign In" leads to an error that I am having trouble debugging (also screenshot below).
What are the proper steps to debugging this? I'm guessing its an issue with Azure being configured correctly. I have OAuth added to the bot, and client Id and Secret from Badgr entered in the correct places. Thanks!
The text was updated successfully, but these errors were encountered: