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
When using the Keycloak-connect npm package, there is a function to generate the logout url: keycloak.logoutUrl.
According to the typescript types, it accepts 2 parameters:
redirectUrl: string (mandatory)
idTokenHint?: string (not-mandatory)
Calling this method with only the mandatory parameter does not gives the expected output.
Version
20.0.2
Expected behavior
When only the mandatory parameter redirectUrl is passed to the function, the generated logout url should contain it.
Actual behavior
The redirectUrl parameter does not get added to the generated logout url unless the optional idTokenHint is passed as well. In this case, both are added to the generated url.
How to Reproduce?
Get a configured setup of keycloak-connect and call the method keycloak.logoutUrl with only 1 parameter. In that case, the parameter value does not get found in the generated logout url
Anything else?
I'll create a PR to fix this
The text was updated successfully, but these errors were encountered:
Describe the bug
When using the Keycloak-connect npm package, there is a function to generate the logout url: keycloak.logoutUrl.
According to the typescript types, it accepts 2 parameters:
Calling this method with only the mandatory parameter does not gives the expected output.
Version
20.0.2
Expected behavior
When only the mandatory parameter redirectUrl is passed to the function, the generated logout url should contain it.
Actual behavior
The redirectUrl parameter does not get added to the generated logout url unless the optional idTokenHint is passed as well. In this case, both are added to the generated url.
How to Reproduce?
Get a configured setup of keycloak-connect and call the method keycloak.logoutUrl with only 1 parameter. In that case, the parameter value does not get found in the generated logout url
Anything else?
I'll create a PR to fix this
The text was updated successfully, but these errors were encountered: