keycloak-scim/js/apps/keycloak-server
Jon Koops c17023270c
Use correct PNPM workspace names on CI (#29973)
Closes #29976

Signed-off-by: Jon Koops <jonkoops@gmail.com>
Signed-off-by: Hynek Mlnarik <hmlnarik@redhat.com>
Co-authored-by: Hynek Mlnarik <hmlnarik@redhat.com>
2024-06-03 13:42:44 +02:00
..
scripts Use correct PNPM workspace names on CI (#29973) 2024-06-03 13:42:44 +02:00
.gitignore Move all JavaScript projects into single PNPM workspace (#24537) 2024-04-02 16:14:58 +02:00
package.json Upgrade JS dependencies to latest version (#29379) 2024-05-08 15:02:45 +02:00
README.md Move all JavaScript projects into single PNPM workspace (#24537) 2024-04-02 16:14:58 +02:00

Keycloak Server

This app allows you to run a local development version of the Keycloak server.

Running the Keycloak server

First, ensure that all dependencies are installed locally using PNPM by running:

pnpm install

After the dependencies are installed we can start the Keycloak server by running the following command:

pnpm start

This will download the Nightly version of the Keycloak server and run it locally on port 8180. If a previously downloaded version was found in the server/ directory then that one will be used instead. If you want to download the latest Nightly version you can remove the server directory before running the command to start the server.

If you want to run with a local Quarkus distribution of Keycloak for development purposes, you can do so by running this command instead:

pnpm start -- --local

All other arguments will be passed through to the underlying Keycloak server.

In order for the development version of the Admin UI to work you will have to import a custom client to the Keycloak server. This is only required during development as the development server for the Admin UI runs on a different port. This client will be imported automatically under the name security-admin-console-v2 when the Keycloak server starts.

This client only allows redirects from/to "localhost:8080" so be sure either modify the client json in ./scripts or only attempt to authenticate and redirect from that address