Initialization error after login on Microsoft Edge

Bug Report or Feature Request (mark with an x)

- [ x ] bug report -> please search for issues before submitting
- [ ] feature request

Versions.

Keycloak v3.1.0.Final Keycloak-Angular (angular6-keycloak3) v.3.0.2 Angular v6.1.4 Angular CLI v6.1.5

Microsoft Edge 42.17134.1.0 Windows 10 v1803 (build 17134.228)

Repro steps.

• Using example ‘keycloak-heros’
• Using Keycloak base installation.
• Updating the ‘keycloak-heros’ keycloakConfig in environment to match.
• Using Microsoft Edge on Windows.
• On loading the app, the screen redirects to Keycloak, I authenticate, and then it redirects back to the app.

The log given by the failure.

ERROR An error happened during Keycloak initialization.

Desired functionality.

Currently shows a blank screen in Microsoft Edge 42 after successful login.

That’s all I get in the log, on trying to throw errors at that point I get problems with adding the error, with the Keycloak instance effectively being null. This is around line 200 of keycloak.service.ts. Although logging it to the console shows its methods (I assume from the typings).

I’ve spent a couple days trying different things, I don’t think it’s CORS, I don’t think it’s caching. On trying to debug with Edge the ‘token’ request comes through without information. My thinking is that Angular isn’t properly initialised before it fires off the token request, and that the module that comes from keycloak-js-bower isn’t making its way through properly.

I’m really stuck with this one, I’ve tried to get to the stage where I can debug (or ‘console.log’…) into the keycloak-js-bower repo but without success.

I would also like to give my thanks to the team for your continued hard work and responsiveness. I’ve previously raised an issue here and was updated very promptly!

Any other help I can provide I will be glad to try with some direction.

Many thanks

[trung674]

I encountered this problem on live server only. It works almost fine in localhost (this bug pops up once in a while)

Edit (07/01/2019): After doing some more experiments, Edge generates this error when:

• The client is deployed locally and the Keycloak server is deployed on live server (without certificate)
• Both the client and Keycloak server are deployed on live servers but both using self-signed certificates.

It seems Edge has some default security policy that prevents Keycloak iframe from being loaded from untrusted source.

[jonkoops]

Closing this issue due to unresponsiveness and the death of Edge.