generated from garronej/ts-ci
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kcContext.auth no longer being set correctly #121
Comments
Thank you for reporting, there is indeed an error on keycloakify's side. |
I thought so too given the fact that it was just i18n, but I bisected the
releases and v5.0.0 was the first release that had this bug.
…On Sun, Jun 19, 2022 at 12:25 PM Joseph Garrone ***@***.***> wrote:
Thank you for reporting, there is indeed an error on keycloakify's side.
I doubt it's the bump to v5 that causes it though....
—
Reply to this email directly, view it on GitHub
<#121 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJEP7M37JZUJSIC2GEULHLVP5CXDANCNFSM5ZF2DXZA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I found the guilty commit. |
@bplotnick it's fixed in latest release, |
I must've messed up my bisect somehow. Glad you tracked down the issue. I've confirmed that I can't repro the issue anymore. Thanks @garronej! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Typically
kcContext.auth
contains fields likeshowTryAnotherWayLink
, which allows users to pick auth methods. However, as of v5.0.0, this is no longer working askcContext.auth
is being set asfalse
.This is easily reproducible - 1) directly observe the value or 2) try with multiple auth methods - the built-in theme will have the link but the keycloakify theme will not.
I've narrowed this down to starting in v5.0.0, but i haven't been able to determine why it is happening.
The text was updated successfully, but these errors were encountered: