This is the documentation for v6, checkout the latest version
Keycloakify
HomeGitHubStartersStorybookDiscordKeycloak-js Alternative
v5
  • Keycloakify
  • Release Notes & Upgrade Instructions
  • FAQ
v5
  • ๐ŸRequirements
  • ๐Ÿ‘จโ€๐Ÿ’ป๐Ÿ‘จ๐Ÿ’ป Quick start
  • ๐ŸงชDevelopment
  • ๐Ÿ“งEmail customization
  • โœ’๏ธTerms and conditions
  • โœ…Realtime input validation
  • โš ๏ธLimitations
  • ๐ŸŒ‰Context persistence
  • ๐ŸŒAdding i18n messages keys
  • โšกPerformance optimization
  • ๐Ÿ’‚Email domain acceptlist
  • ๐Ÿ›‘Keycloak error in log
  • ๐Ÿ’ŸContributing
Powered by GitBook
On this page
  • Some pages still have the default theme. Why?
  • process.env.PUBLIC_URL not supported.
  • @font-face importing fonts from the src/ dir
  • login and email only

Was this helpful?

Limitations

PreviousRealtime input validationNextContext persistence

Last updated 27 days ago

Was this helpful?

Some pages still have the default theme. Why?

This project only support out of the box the most common user facing pages of Keycloak login.

To see the complete list of pages that Keycloak provide you can download the base theme with the following command

npx -p keycloakify download-builtin-keycloak-theme

Most Keycloakify component are based on the base theme of Keycloak v11.0.3 ().

are the pages currently implemented by this module.

I have established that a page that I need isn't supported out of the box by Keycloakify, now what?

Keycloakify also enables you to declare custom ftl pages.

Check out how my-extra-page-1.ftl and my-extra-page-2.ftl where added to .

Main takeaways are:

  • You must declare your custom pages in the package.json.

  • (TS only) You must declare theses page in the type argument of the getter function for the kcContext in order to have the correct typings.

  • (TS only) If you use Keycloak plugins that defines non standard .ftl values (Like for example that define authorizedMailDomains in register.ftl) you should declare theses value to get the type.

  • You should provide sample data for all the non standard value if you want to be able to debug the page outside of keycloak.

process.env.PUBLIC_URL not supported.

You won't be able to . (This isn't recommended anyway).

@font-face importing fonts from the src/ dir

If you are building the theme with this limitation doesn't apply, you can import fonts however you see fit.

Example of setup that won't work

  • We have a fonts/ directory in src/

  • We import the font like this in a .scss a file.

Possible workarounds

  • If it is possible, use Google Fonts or any other font provider.

login and email only

As of now Keycloakify only enable you to create a theme that covers the Login pages and the emails. Acount and Admin Console aren't supported yet.

.

If you want to host your font recommended approach is to move your fonts into the public directory and to place your @font-face statements in the public/index.html. Example (and the font are ).

If you can't or wont move your @font-face statements in the public/index.html, you can still , you will need to enable for your font files, even on the same domain.

If you are missing this feature .

โš ๏ธ
Video demo
Here
๐Ÿ’ŸContributing
the demo project
example
example
this plugin
example
example
import things from your public directory in your JavaScript code (it's supported in public/index.html)
--external-assets
src: url("/fonts/my-font.woff2") format("woff2");
Use --external-assets
here
here
use non relative url
Access-Control-Allow-Origin
open an issue about it