🚀 A starter/demo project for Keycloakify v9 🚀



Authenticated React SPA

# Introduction This repo constitutes an easily reusable setup for a Keycloak theme project OR for a Vite SPA React App that generates a Keycloak theme that goes along with it. If you are only looking to create a Keycloak theme (and not a Keycloak theme and an App that share the same codebase) there are a lot of things that you can remove from this starter: [Please read this section of the README](#standalone-keycloak-theme). This starter is based on Vite. There is also [a Webpack based starter](https://github.com/keycloakify/keycloakify-starter-cra). > 📣 Looking for a library for redirecting your user to Keycloak when they click on the 'Login' button? > Check out [oidc-spa](https://oidc-spa.dev) It's made by us and it's used in the [src/App](https://github.com/keycloakify/keycloakify-starter/tree/main/src/App) of this starter. # Quick start ```bash git clone https://github.com/keycloakify/keycloakify-starter cd keycloakify-starter yarn # install dependencies (it's like npm install) yarn storybook # Start Storybook # This is by far the best way to develop your theme # This enable to quickly see your pages in isolation and in different states. # You can create stories even for pages that you haven't explicitly overloaded. See src/keycloak-theme/login/pages/LoginResetPassword.stories.tsx # See Keycloakify's storybook for if you need a starting point for your stories: https://github.com/keycloakify/keycloakify/tree/main/stories yarn dev # See the Hello World app # Uncomment line 97 of src/keycloak-theme/login/kcContext where it reads: `mockPageId: "login.ftl"`, reload https://localhost:3000 # You can now see the login.ftl page with the mock data. (Don't forget to comment it back when you're done) # Install mvn (Maven) if not already done. On mac it's 'brew install maven', on Ubuntu/Debian it's 'sudo apt-get install maven' yarn build-keycloak-theme # Actually build the theme (generates the .jar to be imported in Keycloak) # Read the instruction printed on the console to see how to test # your theme on a real Keycloak instance. npx eject-keycloak-page # Prompt that let you select the pages you want to customize # This CLI tools is not guaranty to work, you can always copy pase pages # from the Keycloakify repo. # After you ejected a page you need to edit the src/keycloak-theme/login(or admin)/KcApp.tsx file # You need to add a case in the switch for the page you just imported in your project. # Look how it's done for the Login page and replicate for your new page. npx initialize-email-theme # For initializing your email theme # Note that Keycloakify does not feature React integration for email yet. npx download-builtin-keycloak-theme # For downloading the default theme (as a reference) # Look for the files in dist_keycloak/src/main/resources/theme/{base,keycloak} ``` ## Using a development container This starter supports [development containers](https://containers.dev/). You can customize the configuration file [`.devcontainer.json`](./.devcontainer/devcontainer.json) to your liking. Checkout [this video](https://www.youtube.com/watch?v=cB86HE_HIDc) to understand dev containers and how to set up your environment. # Theme variant Keycloakify enables you to create different variant for a single theme. This enable you to have a single jar that embed two or more theme variant. ![Theme variant](https://content.gitbook.com/content/FcBKODbZbNDgm0rc6a9K/blobs/9iKgs2rv2Kfb2pbs4dRz/image.png) You can enable this feature by providing multiple theme name in the Keycloakify build option. [See documentation](https://docs.keycloakify.dev/build-options#themename) # The CI workflow - To release **don't create a tag manually**, the CI do it for you. Just update the `package.json`'s version field and push. - The `.jar` files that bundle the Keycloak theme will be attached as an asset with every GitHub release. [Example](https://github.com/InseeFrLab/keycloakify-starter/releases/tag/v0.1.0). The permalink to download the latest version is: `https://github.com/USER/PROJECT/releases/latest/download/keycloak-theme.jar`. For this demo repo it's [here](https://github.com/codegouvfr/keycloakify-starter/releases/latest/download/keycloak-theme.jar) - This CI is configured to publish [the app](https://starter.keycloakify.dev) on [GitHub Pages](https://github.com/codegouvfr/keycloakify-starter/blob/3617a71deb1a6544c3584aa8d6d2241647abd48c/.github/workflows/ci.yaml#L51-L76) and on [DockerHub](https://github.com/codegouvfr/keycloakify-starter/blob/3617a71deb1a6544c3584aa8d6d2241647abd48c/.github/workflows/ci.yaml#L78-L123) (as a Ngnix based docker image). In practice you probably want one or the other but not both... or neither if you are just building a theme (and not a theme + an app). If you want to enable the CI to publish on DockerHub on your behalf go to repository `Settings` tab, then `Secrets` you will need to add two new secrets: `DOCKERHUB_TOKEN`, you Dockerhub authorization token. `DOCKERHUB_USERNAME`, Your Dockerhub username. We deploy the demo app at [starter.keycloakify.dev](https://starter.keycloakify.dev) using GitHub page on the branch `gh-pages` (you have to enable it). To configure your own domain name update the homepage field of the `package.json` and potentially the `base` option in the `vite.config.ts`. Regarding DNS configuration you can refer to [this documentation](https://docs.gitlanding.dev/using-a-custom-domain-name). - The CI publishes the app docker image on DockerHub. `/:main` for each **commit** on `main`, `/:` for each **pull-request** on `main` and when **releasing a new version**: `/:latest` and `/:X.Y.Z` [See on DockerHub](https://hub.docker.com/r/codegouvfr/keycloakify-starter) ![image](https://user-images.githubusercontent.com/6702424/229296422-9d522707-114e-4282-93f7-01ca38c3a1e0.png) ![image](https://user-images.githubusercontent.com/6702424/229296556-a69f2dc9-4653-475c-9c89-d53cf33dc05a.png) # The storybook ![image](https://github.com/keycloakify/keycloakify/assets/6702424/a18ac1ff-dcfd-4b8c-baed-dcda5aa1d762) ```bash yarn yarn storybook ``` # Docker Instructions for building and running the react app (`src/App`) that is collocated with our Keycloak theme. ```bash docker build -f Dockerfile -t keycloakify/keycloakify-starter:main . docker run -it -dp 8083:80 keycloakify/keycloakify-starter:main # You can access the app at http://localhost:8083 ``` # I only want a Keycloak theme If you are only looking to create a Keycloak theme and not a Theme + a React app, you can run theses few commands to refactor the template and remove unnecessary files. ```bash cd path/to/keycloakify-starter rm -r src/App mv src/keycloak-theme/* src/ rm -r src/keycloak-theme cat << EOF > src/main.tsx import { createRoot } from "react-dom/client"; import { StrictMode, lazy, Suspense } from "react"; import { kcContext as kcLoginThemeContext } from "./login/kcContext"; import { kcContext as kcAccountThemeContext } from "./account/kcContext"; const KcLoginThemeApp = lazy(() => import("./login/KcApp")); const KcAccountThemeApp = lazy(() => import("./account/KcApp")); createRoot(document.getElementById("root")!).render( {(()=>{ if( kcLoginThemeContext !== undefined ){ return ; } if( kcAccountThemeContext !== undefined ){ return ; } throw new Error( "This app is a Keycloak theme" + "It isn't meant to be deployed outside of Keycloak" ); })()} ); EOF rm .dockerignore Dockerfile nginx.conf cat << EOF > .github/workflows/ci.yaml name: ci on: push: branches: - main pull_request: branches: - main jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 - uses: bahmutov/npm-install@v1 - run: yarn build - run: npx keycloakify check_if_version_upgraded: name: Check if version upgrade if: github.event_name == 'push' runs-on: ubuntu-latest needs: test outputs: from_version: \${{ steps.step1.outputs.from_version }} to_version: \${{ steps.step1.outputs.to_version }} is_upgraded_version: \${{ steps.step1.outputs.is_upgraded_version }} steps: - uses: garronej/ts-ci@v2.1.0 id: step1 with: action_name: is_package_json_version_upgraded branch: \${{ github.head_ref || github.ref }} create_github_release: runs-on: ubuntu-latest needs: check_if_version_upgraded # We create a release only if the version have been upgraded and we are on a default branch if: needs.check_if_version_upgraded.outputs.is_upgraded_version == 'true' && github.event_name == 'push' steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 - uses: bahmutov/npm-install@v1 - run: yarn build - run: npx keycloakify - run: mv dist_keycloak/target/retrocompat-*.jar retrocompat-keycloak-theme.jar - run: mv dist_keycloak/target/*.jar keycloak-theme.jar - uses: softprops/action-gh-release@v1 with: name: Release v\${{ needs.check_if_version_upgraded.outputs.to_version }} tag_name: v\${{ needs.check_if_version_upgraded.outputs.to_version }} target_commitish: \${{ github.head_ref || github.ref }} generate_release_notes: true draft: false files: | retrocompat-keycloak-theme.jar keycloak-theme.jar env: GITHUB_TOKEN: \${{ secrets.GITHUB_TOKEN }} EOF ``` You can also remove `oidc-spa`, `powerhooks`, `zod` and `tsafe` from your dependencies.