Closed muhualing closed 5 years ago
That is a older sample. Let me see if I can figure out what's going on
Have you tested your connection in the app portal?
Have you tested your connection in the app portal?
Sure, I tested it and I can get a token.
Good! It means your OAuth is set up right. Investigating!
Just to toss it out there: I believe the issue is the channel. Teams takes some special handling. Can you test your oauth in another channel?
@muhualing , can you please acknowledge? Otherwise we'll have to close the issue.Thanks.
should this have lived in the samples repo?
This belongs in either v3 or sevices repo.
@muhualing I'm closing this for lack of response. If you still need assistance please re-open.
when I tested the auth bot sample, I met 404not found error
SDK Platform: Nodejs SDK Version: 3.16.0 Active Channels: Teams Deployment Environment: Azure Bot Service
Error: GET to 'https://api.botframework.com/api/usertoken/GetToken?userId=29%3A1R5vQA_0_OF8C4zi2Sy5uQs77pFKXs6Jxx1-UW7fABq7XqkNQ_CrL-lstObXd3RL6MVj_UZIC1PQ3fZGh-YdNFA&connectionName=ConnectionNameV2' failed: [404] Not Found
mycode:
The Client id in the OAuth connection is my bot's AppId, the Client secret is my bot's password, and the Tenant ID is the bot's domain. The connection name is also right(the one in Azure)