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

TeamsActivityHandler does not provide handling signin/failure #6824

Open
tracyboehrer opened this issue Jul 22, 2024 · 3 comments
Open

TeamsActivityHandler does not provide handling signin/failure #6824

tracyboehrer opened this issue Jul 22, 2024 · 3 comments
Assignees
Labels
Area: Teams The issue is related to Teams support bug Indicates an unexpected problem or an unintended behavior.

Comments

@tracyboehrer
Copy link
Member

For example:

Type: invoke
Name: signin/failure

Value:
{{
"code": "resourcematchfailed",
"message": "Resource match failed"
}}

@tracyboehrer tracyboehrer added bug Indicates an unexpected problem or an unintended behavior. needs-triage The issue has just been created and it has not been reviewed by the team. Area: Teams The issue is related to Teams support labels Jul 22, 2024
@tracyboehrer tracyboehrer self-assigned this Nov 1, 2024
@tracyboehrer tracyboehrer removed the needs-triage The issue has just been created and it has not been reviewed by the team. label Nov 1, 2024
@c-nielson
Copy link

Hi, I've just run into this exact problem trying to implement SSO auth with teams-ai. When testing connection in Azure portal it's successful, but when running the bot locally through Teams and ngrok I get a 501 Not Implemented response with these exact values. Any information on how to proceed?

@tracyboehrer
Copy link
Member Author

@c-nielson If you are using Teams AI, I would reach out on the repo. They handle SSO a bit differently I think. For a Bot Framework bot, one of the main causes of this is the API Key on the OAuth Identity. It must be "api://botid-{appid}"

@c-nielson
Copy link

You mean for the OAuth connection? Yes, I have it set up that way for both the OAuth in the bot as well as the App ID URI for the app registration. I'll reach out to Teams AI and see if they have any insight. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Teams The issue is related to Teams support bug Indicates an unexpected problem or an unintended behavior.
Projects
None yet
Development

No branches or pull requests

2 participants