keycloak-scim/js/apps/admin-ui
dependabot[bot] 2f45685a44 Bump vitest from 1.1.3 to 1.2.0 in /js
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 1.1.3 to 1.2.0.
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v1.2.0/packages/vitest)

---
updated-dependencies:
- dependency-name: vitest
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2024-01-15 10:30:57 +01:00
..
cypress Add X509 thumbprint to JWT when using private_key_jwt 2024-01-12 16:01:01 +01:00
maven-resources Integrate registration with terms and conditions required action 2024-01-15 10:19:30 +01:00
public Load Admin Console localizations from resource bundles (#24316) 2023-11-13 12:39:46 -05:00
src Add X509 thumbprint to JWT when using private_key_jwt 2024-01-12 16:01:01 +01:00
cypress.config.js Use module type for all packages (#25084) 2023-11-28 12:26:14 +00:00
index.html Add landmark element for loading state for consoles (#26037) 2024-01-09 15:41:26 +00:00
package.json Bump vitest from 1.1.3 to 1.2.0 in /js 2024-01-15 10:30:57 +01:00
pom.xml Include react and react-dom as external dependencies (#24843) 2023-11-20 16:34:03 +00:00
README.md Move from NPM to PNPM (#19839) 2023-05-05 12:03:24 -04:00
tsconfig.json Rework project structure so it matches the main repo 2023-03-07 11:55:19 +01:00
tsconfig.node.json Rework project structure so it matches the main repo 2023-03-07 11:55:19 +01:00
vite.config.ts Bump vitest from 1.1.1 to 1.1.3 in /js (#25969) 2024-01-11 12:17:52 +00:00

Keycloak Admin UI

This project is the next generation of the Keycloak Administration UI. It is written with React and PatternFly 4 and uses Vite and Cypress.

Development

Prerequisites

Make sure that you have Node.js version 18 (or later) installed on your system. If you do not have Node.js installed we recommend using Node Version Manager to install it.

You can find out which version of Node.js you are using by running the following command:

node --version

In order to run the Keycloak server you will also have to install the Java Development Kit (JDK). We recommend that you use the same version of the JDK as required by the Keycloak server.

Running the Keycloak server

See the instructions in the Keycloak server app.

Running the development server

Now that the Keycloak sever is running it's time to run the development server for the Admin UI. This server is used to build the Admin UI in a manner that it can be iterated on quickly in a browser, using features such as Hot Module Replacement (HMR) and Fast Refresh.

To start the development server run the following command:

pnpm run dev

Once the process of optimization is done your browser will automatically open your local host on port 8080. From here you will be redirected to the Keycloak server to authenticate, which you can do with the default username and password (admin).

You can now start making changes to the source code, and they will be reflected in your browser.

Building as a Keycloak theme

If you want to build the application using Maven and produce a JAR that can be installed directly into Keycloak, check out the Keycloak theme documentation.

Linting

Every time you create a commit it should be automatically linted and formatted for you. It is also possible to trigger the linting manually:

pnpm run lint

Integration testing with Cypress

This repository contains integration tests developed with the Cypress framework.

Prerequisites

Ensure the Keycloak and development server are running as outlined previously in this document.

Running the tests

You can run the tests using the interactive graphical user interface using the following command:

pnpm run cy:open

Alternatively the tests can also run headless as follows:

pnpm run cy:run

For more information about the Cypress command-line interface consult the documentation.

Project Structure

You can find information about the project structure in the official Cypress documentation. Read more about how to write tests