Javascript errors on Forgot Password on Graph API on Windows desktop interactive login screen

Question

Hi All,

We have a windows desktop application that calls the Microsoft Graph API to open the Microsoft login page and authenticate to our Azure Active Directory. Here is the URL:

https://graph.microsoft.com/v1.0/me

Based on calling that endpoint it will call the Microsoft login page for the login:

https://login.microsoftonline.com/common/oauth2/v2.0/NativeClient

When the users try to to use the Forgot Password option we are getting several javascript errors that make it impossible to reset the password such as can be seen below. When the page opens we get several errors. Then when we click next we get several more. Then when we click next again we get several more and then there is no option to proceed with the reset. The initial error is a syntax error to the reset URL:

An error has occurred in the script on this page
Line: 48
Char: 5
Error: Syntax error
Code: 0
URL: https://passwordreset.microsoftonline.com/js/Common.js

I am going back and forth between support and my dev team with each blaming the other. If I can't get a solution to the issue I at least need some help determining who is responsible for investigating this error. Based on what I have seen on the code all we are doing is calling the Microsoft Graph API and then waiting for the response with the authentication token from the interactive login. So that makes me think it lies on the Microsoft side of things.

Please let me know if any further details are needed, thanks!

Answer 1

Hi All,

It looks like this issue has been resolved by Microsoft on their side. But to provide everyone some information on the solution I will note it here.

As it turns out we are using the MSAL SDK to open the interactive login. Based on talking to support it appears this uses System.Windows.Forms to it opens in an IE7 window. Since in my testing we identified that the SSPR/Forgot Password functionality was not working on IE11 it seems likely that there was a bug with this function and Internet Explorer. It seems like there was probably some change on the SSPR that broke it for internet explorer and they fixed it.

I hope this can provide some help for other people.