keycloak is not initialized in hooks

See original GitHub issue

Describe the bug In createReactKeycloakContext initialized is set to false and looks like it never becomes true. When calling keycloak.login() I am getting that adapter property inside keycloak.js is undefined, that seems to be possible if keycloak wasn’t initialized.

I am not sure if it’s related to hooks initialized property at all though.

Use-case scenario:

I am writing a PrivateRoute for Gatsby.js and am using useKeycloak similar to how it’s shown in react-router examples. When being redirected back from keycloak authentication to my page I get Cannot read property 'login' of undefined pointing that adapter is undefined and keycloak isn’t properly inited

KeycloakProvider is present in the hierarchy and some kind of keycloak is provided by useKeycloak with my realm settings. It’s just doesn’t seem to be properly initialized

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:13

Top GitHub Comments

1reaction

punithbmcommented, Jul 9, 2020

@panz3r Hello, can you please check on this. We’re also facing a similar issue and not able to identify a solution. We’re getting keycloak is not initialized in the hooks on refreshing the page

0reactions

aelfriccommented, Jul 9, 2020

I didn’t realize when I first commented on this issue that you were using Gatsby. I expect the issue is that your code is running during the server-side rendering phase and not in the browser.

I have not used it myself, but I think for Gatsby you’d need to follow or borrow from the NextJS example provided in this repository. The essential thing is to wrap Keycloak initialization with a check for whether it’s running in the browser. The recommended way to do that seems to be if(typeof window !== 'undefined')