Script Error when clicking the link Sign out and sign in with a different account

[JosephFicara]

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I am using the un-modified Desktop-App-calls-Web-API" TodoListClient and TodoListService" sample configured in my Azure AD tenant per the instructions on github.

I reproduced this both with the Microsoft.Identity.Web v1.4.0 nuget package, which is the one the source code un-modified uses as well as the latest version v1.4.1 of the Microsoft.Identity.Web nuget package

I am using the "Azure AD Free" SKU of Azure AD, however I have also reproduced this using the P2 SKU of Azure AD

1. Sign in with a valid account in your tenant

2. Click the "Clear Cache" button

3. Click the "Sign in" button

4. Enter the email address of another valid Microsoft account. By Microsoft account I mean an account created using https://account.microsoft.com/account

Note: This account does not have to be in your tenant but if it is in your tenant the account must be added as a Guest account in Azure AD.

5. Click "Next"
6. Click the "Sign out and sign in with a different account." link
7. Observe the "Script Error" Dialog with the following information
   An error has occurred in the script on this page.
   Line: 202
   Char: 337
   Error: Object doesn't support property or method attachEvent'
   Code: 0
   URL: https://login.microsoftonline.com/login.srf?
   wa=wsignoutcleanup1.0&sid=M.10653612753695256942&iss=h ttps://login.live.com
   Do you want to continue running scripts on this page?

Any log messages given by the failure

No

Expected/desired behavior

The "Sign in to your Microsoft account" user interface presents the "Enter Password" screen and you are able to login, assuming the account is a valid account in your tenant. If the account is not a valid account in your tenant then the standard error message should appear.

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows 10

Versions

Version 20H2 (OS Build 19042.685)

Mention any other details that might be useful

This not only happens with the sample code but with custom applications I have built that utilize the MSAL.

If you click the "No" or "Yes" button on the JavaScript error page, typically 2-3 times, the "Sign in to your Microsoft account" screen is presented.

---

Thanks! We'll be in touch soon.

[StephenStaats]

I am having this same issue

[Shama-K]

@JosephFicara and @StephenStaats, To get an idea of how long the issue has been there, could you please share when did you started facing it?

[JosephFicara]

I started seeing this about three months ago, in November 2020. That is when I started the integration work with the MSAL. I don't know if it existed prior to that.

[StephenStaats]

I also started noticing the problem in November 2020. From: JosephFicara [mailto:[email protected]] Sent: Sunday, January 24, 2021 8:15 PM To: Azure-Samples/active-directory-dotnet-native-aspnetcore-v2 Cc: StephenStaats; Mention Subject: Re: [Azure-Samples/active-directory-dotnet-native-aspnetcore-v2] Script Error when clicking the link Sign out and sign in with a different account (#182) I started seeing this about three months ago, in November 2020. That is when I started the integration work with the MSAL. I don't know if it existed prior to that. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#182 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOR5CDHSQA3ABIREAL3BKPDS3TAZBANCNFSM4V4VTLTA> . <https://github.com/notifications/beacon/AOR5CDG4C3MDJZYU6ELNJGTS3TAZBA5CNFSM4V4VTLTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFWXY7NA.gif>

[JosephFicara]

Are there any updates to this issue in terms of a resolution?

[Shama-K]

We have raised an incident with the respective service team and it's in progress.

[JosephFicara]

Thank you!