Sp-dev-docs: AadHttpClient - Error: Window closed without authenticating

[sortegamartin]

Category

• [ ] Question
• [ ] Typo
• [X] Bug
• [ ] Additional article idea

Version

SharePoint Framework 1.4.1

Expected or Desired Behavior

When I add multiple webparts and extensions on the same page and each webpart and extension creates an instance of the AadHttpClient object and then invoke the methods get or post, the following error occurs: "Error: Window closed without authenticating".

This situation only occurs the first time, when you do not have the token yet, the second time you access the page, as the token is saved in the session storage, the error does not occur.

Do you know if there is any way to control this error or if it is a bug?

Thanks!

[waldekmastykarz]

Do all these web parts and extensions try to get access token for the same resource (API) or different ones?

[sortegamartin]

For the same resource (API)

[waldekmastykarz]

I suspect the issue to be with ADAL which might not be made for this scenario, but it would be good to verify/debug.

[xdelgado]

I have the same problem. This will cause that the solution won't be workable in case that you add several client webparts in the same page with AadHttpClient.

[mpasarin]

Thanks for your feedback @sortegamartin
We are currently investigating the issue and we'll get back to you with updates once it's fixed.

[calin1611]

I encountered the same issue while having an instance of AadHttpClient and an instance of AadTokenProvider. Therefore I suspect the issue is at least at the level of AadTokenProvider and not AadHttpClient.

[dgaeta]

@sortegamartin Thanks for bringing this issue to light. We have checked in the fix where there will no longer be popups for the authentication to avoid this issue. The fix will be rolling out sometime next week.

Please feel free to reopen this if the problem persists after next week.

[Nasicus]

@dgaeta any news on this? Doesn't look like there is a new version yet, yes? Will this result in a new SPFx version?
And will this by any chance, solve the issue, that it doesn't work in IE and edge?
See: https://github.com/SharePoint/sp-dev-docs/issues/1556#issuecomment-379740104

[Tiliavir]

@dgaeta "Please feel free to reopen this if the problem persists after next week." - so I guess this should be brought back to live? Can neither see it working nor any attempt of a solution so far ...

[msft-github-bot]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues