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
login-idp-link-confirm.ftl takes a long time to load. As a result , it gives 500.
login-idp-link-email.ftl (you can see it after fixing the template login-idp-link-confirm.ftl). It takes a long time to load, but template works
How to fix:
The problem is in .data_model.identityProviderBrokerCtx and .data_model.brokerContext. But .data_model.brokerContext.username is used in login-idp-link-email.ftl. I found all the keys in brokerContext and calculated the keys that break the template: ["contextData", "idpConfig", "idp", "authenticationSession"].
Hi @Ann2827,
Thank you for the detailed issue, I didn't implement this page, it's from the community.
Unfortunately I have no time to deal with keycloaky issues right now.
I will happily merge your PR though
You deserve to appear in the contributor list!
Hi!
It's me again. I have a problem with templates
login-idp-link-confirm
andlogin-idp-link-email
. She's linked with keys again.How to reproduce the problem:
register.ftl
)login.ftl
via GitHubProblems:
login-idp-link-confirm.ftl
takes a long time to load. As a result , it gives 500.login-idp-link-email.ftl
(you can see it after fixing the templatelogin-idp-link-confirm.ftl
). It takes a long time to load, but template worksHow to fix:
The problem is in
.data_model.identityProviderBrokerCtx
and.data_model.brokerContext
. But.data_model.brokerContext.username
is used inlogin-idp-link-email.ftl
. I found all the keys inbrokerContext
and calculated the keys that break the template: ["contextData", "idpConfig", "idp", "authenticationSession"].New exceptions for .data_model object:
The text was updated successfully, but these errors were encountered: