login.ftl generates keycloak errors
See original GitHub issueOn every request to login.ftl generated by keycloakify the following error is displayed in the keycloak logs:
[freemarker.runtime] Error executing FreeMarker template part in the #attempt block: freemarker.core.InvalidReferenceException: The following has evaluated to null or missing:
object[key] [in template "login.ftl"] at line 70, column 37
The page works fine but it generates a lot of misleading messages in our logs. Any chances to fix that issue?
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:5
Top Results From Across the Web
keycloak-theme/error.ftl at master - GitHub
keycloak -theme/login/error.ftl · Go to file T · Go to line L · Copy path · Copy permalink.
Read more >Keycloak FTL: how can we access error messages within the ...
ftl page that I'd like to display the error messages in. How can I either pass that message down to the login.ftl file...
Read more >Base theme login crashes when message needs to be displayed
Using base theme produces an error when login page tries to display a message. The following properties that are not defined in base...
Read more >Action URI not set error - Getting advice - Keycloak Discourse
This is triggered for yet unknown causes and “usually” when someone tries to login. Keycloak works fine (i.e I can login, logout, use...
Read more >Server Developer Guide - Keycloak
For example to create a custom login form for the mytheme theme copy themes/base/login/login.ftl to themes/mytheme/login and open it in an ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We’ve been using version
4.2.10
. Upgrade to4.2.14
fixed the issue. Thanks.This is the commit where I did the migration from v4 to v5 in the demo app: https://github.com/garronej/keycloakify-demo-app/blob/a5b6a50f24bc25e082931f5ad9ebf47492acd12a/src/index.tsx#L46-L63