You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The typescript sample DOES work with current v1.4.0 MSAL and "redirect"...
But the "redirect" technique breaks when adding browser policies: BlockThirdPartyCookies, DefaultPopupsSetting.
These settings are common to US government computers:
BlockThirdPartyCookies: shouldn't affect well behaved cookies like microsoft logins!?
DefaultPopupsSetting: "Do not allow any site to show popups" shouldn't affect the redirect technique!?
Clicking on the redirect checkbox counts down, allows login via login.microsoftonline.com, then goes back to sample page with the unchaned "Automatic Redirect" and "Authentication Values" boxes, but the "Errors" box says
If authentication fails, this box will have the errors that occurred
errorCode: popup_window_error
errorMessage: Error opening popup window. This can happen if you are using IE or if popups are blocked in the browser.
Strange to see "opening popup window" when using the "redirect" mode sample.
(Note the same policies now exist in MS Edge since it now has the same Chromium engine.)
Expected behavior
Expected the typescript sample to work in "redirect" mode.
Expected the popup blocker policy not to break it.
(I did expect that the popup blocker would break the "popup" mode, so I didn't even try that).
Run the sample. Verify that "redirect" mode works for login.
Set policies in windows for Chrome:
Add to file BlockAndNoPop.reg and run it
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome]
"BlockThirdPartyCookies"=dword:00000001
"DefaultPopupsSetting"=dword:00000002
Remove these two entries selectively afterward via regedit, or if you are sure you have no other policies, you can use this to delete the Chrome key values:
Windows Registry Editor Version 5.00
[-HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome]
Start Chrome & verify policies
Check, and reload the policies (if necessary) with this to ensure they are enabled:
chrome://policy/
Should show both the policies are active.
Library versions
react-aad-msal
: Current (2.3.5)msal
: Current (1.4.0)Describe the bug
The typescript sample DOES work with current v1.4.0 MSAL and "redirect"...
But the "redirect" technique breaks when adding browser policies: BlockThirdPartyCookies, DefaultPopupsSetting.
These settings are common to US government computers:
Clicking on the redirect checkbox counts down, allows login via login.microsoftonline.com, then goes back to sample page with the unchaned "Automatic Redirect" and "Authentication Values" boxes, but the "Errors" box says
Strange to see "opening popup window" when using the "redirect" mode sample.
(Note the same policies now exist in MS Edge since it now has the same Chromium engine.)
Expected behavior
Expected the typescript sample to work in "redirect" mode.
Expected the popup blocker policy not to break it.
(I did expect that the popup blocker would break the "popup" mode, so I didn't even try that).
To Reproduce
Steps to reproduce the behavior:
https://github.com/syncweek-react-aad/react-aad/tree/master/samples/react-typescript
Add to file
BlockAndNoPop.reg
and run itRemove these two entries selectively afterward via regedit, or if you are sure you have no other policies, you can use this to delete the Chrome key values:
Start Chrome & verify policies
Check, and reload the policies (if necessary) with this to ensure they are enabled:
chrome://policy/
Should show both the policies are active.
Run the sample
(See generated console errors below)
Desktop (please complete the following information):
Portion of console log
The text was updated successfully, but these errors were encountered: