Oidc-client-js: signinRedirect doesn't work in Microsoft Edge

[pielegacy]

The following snippet (AuthOIDC being an encapsulating object).

AuthOIDC.userManager.getUser().then(async (user) => {
                if (!user || requiresNewUser) {
                    await AuthOIDC.userManager.signinRedirect();
                }
                else {
                    AuthOIDC.currentUser = user;
                }
            });

Does not work in Microsoft Edge, despite working as expected in Chrome and Firefox.

The only output that I am given even after turning on logging is what follows:

[brockallen]

perhaps a cross-zone issue?

[pielegacy]

Any recommended fixes?

[brockallen]

For what? Have you isolated the issue?

[pielegacy]

Well I know the same snippet of code works fine in all other browsers and it is most definitely that method call that doesn't work. So is there any fixes or things wrong with how I am using the library that would result in this now working in Edge?

[brockallen]

I've not tried to repo it, but from all my prior testing everything worked in edge. So maybe something in a recent update? So either track down the actual reason yourself, or wait for me to have tim to try to reproduce.

[brockallen]

Any update?

[arthurdent510]

I can verify that I am seeing the same thing in Edge. IE is throwing fits for me if running in anything under ie11 mode and if compatibility mode is turned on. Once those are set, it's fine. Edge throws this no matter what combination of settings I use:

SCRIPT7002: XMLHttpRequest: Network Error 0x2efd, Could not complete the operation due to error 00002efd.
ERROR Error: Uncaught (in promise): Error: Network Error

So far, I haven't found much, other than that Edge doesn't like not having a charset defined in the network request. Not sure if that's the issue here or not...

[brockallen]

Ok, I'll try to test it when I can to see if I can repro.

[akiander]

We are experiencing the same kind of behavior in the Microsoft Edge browser. We are trying to use oidc-client with an Angular5 web application. It works fine on Chrome/FireFox but not Edge... the error we see is:

ERROR Error: Uncaught (in promise): Error: Network Error Error: Network Error at Anonymous function (eval code:74:10545) at ZoneDelegate.prototype.invoke (eval code:386:13) at onInvoke (eval code:4961:17) at ZoneDelegate.prototype.invoke (eval code:386:13) at Zone.prototype.run (eval code:138:17) at Anonymous function (eval code:858:17) at ZoneDelegate.prototype.invokeTask (eval code:419:13) at onInvokeTask (eval code:4952:17) at ZoneDelegate.prototype.invokeTask (eval code:419:13) at Zone.prototype.runTask (eval code:188:21)

Was there any determination of what may be happening here?

[brockallen]

Was there any determination of what may be happening here?

Perhaps test the samples in edge (without angular) to see if it's a browser or angular issue? They are here: https://github.com/IdentityServer/IdentityServer4.Samples/tree/release/Clients/src/JsOidc

I can tell you I have tested them, and edge is working for me :)

[akiander]

@brockallen - I confirmed that the oidc-client works fine in MS Edge and IE, so the issue is not with the oidc-client library. It must be because we are trying to use it from within an Angular5 application. We implemented an Angular routing guard that uses this library to authenticate when the user is not logged in but it's just not working for MS Edge and IE so I guess we'll have to find another library for this.

[akiander]

I finally found the cause of this issue... the client definition I was using was missing this entry:

AllowAccessTokensViaBrowser = true,

Once I added that, the redirect happens as expected.

[lghinet]

i am having the same issue, using react,
network error, nothing more in ms edge, onsigninredirect
could it be because i use http and not https

[lghinet]

https://github.com/IdentityServer/IdentityServer4.Samples/tree/release/Clients/src/JsOidc
is not working on MS Edge v40.15063.674.0

[sei-jmattson]

We were troubleshooting this issue in MS Edge v40.15063.674.0, but now find it
works again in Microsoft Edge 41.16299.15.0. Hate to leave clients behind, but hey, if you aren't leaning forward you are falling backward!

[amojicamu]

You may run into this issue regardless of Edge version. Tested in Edge v41.16299.726.0. The problem in my case was indeed a cross-zone issue as @brockallen mentioned. It turns out cross-zone XMLHttpRequest redirect gets blocked by Edge.

I had the client app running at http://localhost:8632, the authority at http://authority.my.company.com

http://localhost is considered "Internet" zone, while http://authority.my.company.com is "Local Intranet"
Notice Edge takes these settings from IE.

One way to test it is setting the client under http://localhost.my.company.com:8632 an alias that in the host file. In order for Edge to grab the configuration you have to run this command in console as administrator

CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe"

After both sites are under the same zone the problem goes away.

I doubt even switching to another library will fix this as long as they are in different zones. Works for me in Angular 7