No description
Find a file
dependabot[bot] e5e7fa202d Bump @typescript-eslint/parser from 5.27.0 to 5.27.1
Bumps [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser) from 5.27.0 to 5.27.1.
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v5.27.1/packages/parser)

---
updated-dependencies:
- dependency-name: "@typescript-eslint/parser"
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2022-06-13 11:00:13 +02:00
.github Lock React and related dependencies to version 17 (#2616) 2022-05-11 07:22:58 +02:00
.husky Stop running unit tests on commit (#1148) 2021-09-13 11:28:47 +02:00
cypress Changed to use one confirm dialog (#2722) 2022-06-01 11:12:30 +02:00
images Replace development server with nightly version of Keycloak (#2395) 2022-04-08 19:32:44 +02:00
keycloak-theme Bump nexus-staging-maven-plugin from 1.6.12 to 1.6.13 in /keycloak-theme 2022-04-25 11:33:34 +02:00
mocks Check types using ts-jest and upgrade Jest (#1178) 2021-09-17 09:33:15 +02:00
public Add a 'Reset' button the the events search form (#2732) 2022-06-02 09:27:57 +02:00
scripts Upgrade to version 18 of Node.js (#2474) 2022-04-21 16:52:49 +02:00
src added tag to make sure we override (#2783) 2022-06-11 16:13:06 +02:00
themes Upgrade to Snowpack 3 (#839) 2021-07-16 10:59:46 +02:00
types Configure Cypress to use the correct types (#1168) 2021-09-17 15:23:34 +02:00
.eslintrc.js Replace Lodash with it's ESM variant (#1990) 2022-02-02 11:33:57 +01:00
.gitignore Add nexus profile for releases (#1704) 2021-12-15 14:00:56 +01:00
.prettierrc.json added initial version of the "help system" (#26) 2020-09-02 09:51:42 +02:00
CODING_GUIDELINES.md Add section to code guidelines about non-null assertions (#889) 2021-07-22 23:32:10 +02:00
cypress.json Enable tests retries for Cypress (#2443) 2022-04-12 09:11:16 -04:00
get-version.sh Use Maven for versioning and drop NPM version (#1336) 2021-10-14 11:00:49 +02:00
jest.config.ts Replace Lodash with it's ESM variant (#1990) 2022-02-02 11:33:57 +01:00
jest.setup.ts Check types using ts-jest and upgrade Jest (#1178) 2021-09-17 09:33:15 +02:00
LICENSE Initial commit 2020-07-27 14:40:12 -04:00
MAINTAINERS.md Add maintainers file (#1576) 2021-11-20 13:54:50 +01:00
package-lock.json Bump @typescript-eslint/parser from 5.27.0 to 5.27.1 2022-06-13 11:00:13 +02:00
package.json Bump @typescript-eslint/parser from 5.27.0 to 5.27.1 2022-06-13 11:00:13 +02:00
postcss.config.js Update to PF-4.183 (#2216) 2022-03-10 10:41:47 +01:00
README.md Upgrade to version 18 of Node.js (#2474) 2022-04-21 16:52:49 +02:00
release.sh Drop snapshot releases in favour of nightlies (#2340) 2022-03-28 09:18:40 +02:00
set-version.sh Use Maven for versioning and drop NPM version (#1336) 2021-10-14 11:00:49 +02:00
snowpack.config.mjs Change local development and ci to quarkus (#2115) 2022-03-06 16:25:37 +01:00
tsconfig.eslint.json Lint all files in the project (#1167) 2021-09-16 12:24:21 +02:00
tsconfig.jest.json Update to Jest 28 (#2566) 2022-05-03 14:10:17 +02:00
tsconfig.json Configure Cypress to use the correct types (#1168) 2021-09-17 15:23:34 +02:00

Keycloak Admin UI

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

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

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

npm install

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

npm run server: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.

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 (more on that later).

Wait for the Keycloak server to be up and running and run the following command in a new terminal:

npm run server:import-client

You'll only have to run this command once, unless you remove the server directory or Keycloak server data.

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:

npm run start

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:

npm run lint

Theming

It's possible to theme the Admin UI interface, this is useful if you want to apply your own branding so that the product looks familiar to your users. The Admin UI comes with two built-in themes called keycloak and rh-sso, by default the keycloak theme will be used when building the application.

This behavior can be changed by passing in a THEME_NAME environment variable, for example if wanted to build the application using the rh-sso theme we can do the following:

THEME_NAME=rh-sso npm run build

And likewise if we wanted to start a development server with this theme:

THEME_NAME=rh-sso npm run start

To make it simpler to build the rh-sso theme there are some shorthand NPM scripts available that you can run instead:

# Run a production build with the 'rh-sso' theme
npm run build:rh-sso

# Or for development
npm run start:rh-sso 

Creating your own theme

All themes are located in the themes/ directory of the project, if you want to create a new theme you can create a new directory here and name it the same as your theme. Copy the files from the default theme here and customize them to your liking.

Keycloak UI Test Suite in Cypress

This repository contains the UI tests for Keycloak developed with Cypress framework

Prerequisites

via Cypress Test Runner

By using npx:

note: npx is included with npm > v5.2 or can be installed separately.

npx cypress open

After a moment, the Cypress Test Runner will launch:

test_runner

via terminal

By executing:

$(npm bin)/cypress run

...or...

./node_modules/.bin/cypress run

...or... (requires npm@5.2.0 or greater)

npx cypress run

To execute a specific test on a specific browser run:

cypress run --spec "cypress/integration/example-test.spec.js" --browser chrome

note: the complete list of parameters can be found in the official Cypress documentation.

Read more about how to write tests

Project Structure

/assets (added to .gitignore)
  /videos - if test fails, the video is stored here
  /screenshots - if test fails, the screenshot is stored here
/cypress
  /fixtures - external pieces of static data that can be used by your tests
  /integration - used for test files (supported filetypes are .js, .jsx, .coffee and .cjsx)
  /plugins
    - index.js - extends Cypress behaviour, custom plugins are imported before every single spec file run
  /support - reusable behaviour
    - commands.js - custom commands
    - index.js - runs before each test file

/cypress.json - Cypress configuration file
/jsconfig.json - Cypress code autocompletion is enabled here

note: More about the project structure in the official Cypress documentation.

License