-
Notifications
You must be signed in to change notification settings - Fork 515
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
Copilot OAuth #11966
Comments
Hello @mathihalli,
This information will help us better understand the situation and provide a more accurate response. |
Hi Team,
Please see the details below:
1. Documentation links: We followed the examples outlined here:
-
https://learn.microsoft.com/en-us/microsoft-365-copilot/extensibility/overview-declarative-agent
- https://github.com/microsoftgraph/msgraph-sample-copilot-plugin
-
https://github.com/OfficeDev/Microsoft-365-Copilot-Samples/tree/main/samples/cext-trey-research-auth
For OAuth, we followed the instructions outlined here:
https://learn.microsoft.com/en-us/microsoft-365-copilot/extensibility/api-plugin-authentication
2. Teams client version: We use the browser version of Teams (v2)
3. Code snippets:
- Because we don't have our own OAuth server, we use the Microsoft login
as our proxy. Accordingly. We've configured the login.microsoftonline.com
as our OAuth server (in dev.teams.microsoft.com). I've attached the
screenshot to this email.
- We've configured the
https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect as a redirect
URL in our app registration (attached screenshot)
The core issue was that this was working till Monday (3 days ago). It
suddenly stopped working now.
Hope this helps
Thanks
-Madhu
…On Fri, 20 Dec 2024 at 00:01, sayali-MSFT ***@***.***> wrote:
Hello @mathihalli <https://github.com/mathihalli>,
Thank you for your inquiry about your Teams app development issue! To
assist you better, could you please provide the following details?
1. Documentation Links: Any specific documentation you followed that
relates to your problem.
2. Teams Client Version: What version of the Teams client are you
using?
3. Code Snippets: Relevant code snippets that illustrate the issue.
This information will help us better understand the situation and provide
a more accurate response.
—
Reply to this email directly, view it on GitHub
<#11966 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AENJF4JJIDHG3JQPEZJSL3D2GPFEBAVCNFSM6AAAAABT6PW4ACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJWGQ3TKNJXGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@mathihalli -The error you're encountering, "Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://login.microsoftonline.com') does not match the recipient window's origin ('https://teams.microsoft.com')", indicates a mismatch between the target origin specified in the postMessage call and the origin of the recipient window.
Could you please also raise the issue here to seek guidance related to Teams Toolkit: -https://github.com/OfficeDev/teams-toolkit/issues |
Steps to reproduce
Now, try to access (via copilot) the app and it should prompt you to Sign in. When you click on the sign-in button, the login fails and you'll see this error in the console logs
Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://login.microsoftonline.com') does not match the recipient window's origin ('https://teams.microsoft.com').
Expected behavior
The sign-in should happen and the successful auth should've been posted to the Teams window
Actual behavior
The sign-in popup shows a blank screen and the console logs has this warning message:
Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://login.microsoftonline.com') does not match the recipient window's origin ('https://teams.microsoft.com').
Error details
The sign-in button was working till ~2 days ago
The text was updated successfully, but these errors were encountered: