Skip to content
This repository has been archived by the owner on Jan 16, 2024. It is now read-only.

Latest commit

 

History

History
35 lines (25 loc) · 2.27 KB

SSOREADME.MD

File metadata and controls

35 lines (25 loc) · 2.27 KB
Raw

Keycloack:

1 Frontend configuration

ui/src/keycloak/index.ts

ui/public/keycloak.json

For more details about this options see docs

2 Backend configuration

src/main/resources/application.yaml -> keycloak:

For more details about this options see docs

3 Adding new user
  1. We use use-resource-role-mappings: true in application.yml, so roles must be added at "client" level. To add new role go to Configure -> Clients, then drill-down in "tesler-keycloak-client", select tab "Roles" and press "Add role"
  2. Create user docs
  3. In "Client Roles" select "tesler-keycloak-client" and add at least one role docs
  4. Add new roles in dictionary, e.g. add them in TESLER-DICTIONARY_ITEM.csv. For example, if you added role "NEW_ROLE", then csv will have this line:
ID;DICTIONARY_TYPE_ID;TYPE;KEY;VALUE;ACTIVE;DISPLAY_ORDER;DESCRIPTION
"100";1;"INTERNAL_ROLE";"NEW_ROLE";"New Role";true;0;null
4 Saving keycloak configuration changes to git (realm, client, users and so on)

Keycloak in docker-compose.yml is configured to import configuration from /docker/keycloak-config on container startup using keycloak.migration.action=import docs

By default in will not override changes made in UI on container restart, because keycloak.migration.strategy=IGNORE_EXISTING is used docs

To save changes made in UI to git one can change keycloak.migration.action=import to keycloak.migration.action=export in docker-compose.yml and delete and start new container. All changes will be present in /docker/keycloak-config. Please, do not forget to set keycloak.migration.action=import back

5 Clean keycloak start

delete .tmp folder, then delete and start keycloack container