githubEdit

🏁Requirements

circle-exclamation
circle-check

Supported Keycloak version

chevron-rightSee versions Keycloakify have been tested withhashtag

Latest release isn't in the list yet? It probably works fine, we just can't confirm it yet.

Supported React frameworks

circle-check
chevron-rightSee morehashtag

This tool assumes you are bundling your app with Webpackarrow-up-right.

It assumes there is a build/ directory at the root of your react project directory, it's usually generated after running yarn build.

The build/ directory is expected to contain an index.html file and a build/static/ directory.

Keycloakify also assumes there is a public/ directory at the root of your react project that is used to make static files available.

Concretely Keycloakify assumes that if there is a public/a/b.c/foo.txt file. This file should be available at https://localhost:<some_port>/a/b/c.foo.txt when running your app in test mode (usually by firing yarn start).

For more detailed information see this issuearrow-up-right.

My framework doesn’t seem to be supported, what can I do?

Currently Keycloakify is only compatible with SPA React apps. It doesn’t mean that you can't use Keycloakify if you are using Next.js, Express or any other framework that involves a server but your Keycloak theme will need to be a standalone project. Find specific instructions about how to get started herearrow-up-right.

To share your styles between your main app and your login pages you will need to externalize your design system by making it a separate module. Checkout ts_ciarrow-up-right, it can help with that (example with our design systemarrow-up-right).

Utility that needs to be installed

  • mvn (Mavenarrow-up-right), rm, mkdir, curl, unzip.

  • docker must be up and running when running start_keycloak_testing_container.sh

Last updated

Was this helpful?