MicrosoftEdge-Extensions
MicrosoftEdge-Extensions copied to clipboard
Extension making AJAX requests doesn't get authentication cookies appended
On edge, when a user is logged in to his identity provider (Azure AD), an ajax request to the IDP URL from an extension gets rejected as if the user is not logged in. Making the same request from a webpage, works as expected. To my understanding, it has something to do with the PRT mechanism. If Edge wouldn't wrap the identification by itself, making requests to the IDP from the extension would just work - because it is based on cookies. But when Edge is managing the process - the cookies are not saved to the domain. Instead, they are appended to each network request created by the web page. Why isn't the same mechanism apply for requests created by the Extension? Can we get ajax requests to the IDP work? We need a way to get "inside" the PRT mechanism
This issue is being tracked and it's currently in our backlog.
@nagachaitanyalokam Any progress on this? We also faced this issue.
Hi @joesh36, @nagachaitanyalokam isn't working anymore with us now. I will look into it & keep you posted.
Hey @sivsouvamMSFT, any news about this one?
Hi @eadan-y, the issue is being tracked. It's on our backlog. I will be sharing updates on it soon.
Hi @eadan-y, to better assist you, we need some additional information:
-
Does this issue occur in the Chrome browser as well, specifically for AD/Entra ID?
-
Can you confirm if the call was made from a Background Script or a Content Script? We suspect it might be the Content Script, but we would like to confirm.
-
Does this issue also reproduce with a Fetch call?
-
Could you please share a sample of the code that is not working?
We understand that this issue has been ongoing for two years, and we appreciate your patience. Gathering this information will help us provide a more accurate and effective solution.
Thank you for your cooperation.
Hey @eadan-y, could you please provide us the addition information.
- The issues does not happen on Chrome.
- The call is done from a background script.
- The call is done with Fetch.
- I will try to create a demo extension, but since it has to be with a user-authentication for azure, it will be hard to illustrate.