Keycloak docker container issue

[borispopicbusiness]

The issue with the Keycloak Docker container remains unresolved. However, my research has yielded some insights. I am currently preparing the materials for a customized Docker image. The main challenge is that Keycloak is unable to import the advanced tt_realm_config.json file, which was exported from a non-Dockerized Keycloak installation on the malfunctioning workstation.

[borispopicbusiness]

This was the root of the problem. I deleted them, and the file was uploaded successfully.
Check this link for further analysis:
keycloak/keycloak#11664

I will add some temporary remarks regarding the issue to README.md and push it to the master branch. I will also update tt_realm_config.json and push it to the develop branch, continuing to test everything until it is fully polished.

      {
        "id": "6c75eed2-f25c-4c61-8700-1f1e31d91a0e",
        "name": "Default Policy",
        "description": "A policy that grants access only for users within this realm",
        "type": "js",
        "logic": "POSITIVE",
        "decisionStrategy": "AFFIRMATIVE",
        "config": {
          "code": "// by default, grants any permission associated with this policy\n$evaluation.grant();\n"
        }
      },
      {
        "id": "60151eef-11be-4817-be0c-f94385f51631",
        "name": "Default Permission",
        "description": "A permission that applies to the default resource type",
        "type": "resource",
        "logic": "POSITIVE",
        "decisionStrategy": "UNANIMOUS",
        "config": {
          "defaultResourceType": "urn:tt_client:resources:default",
          "applyPolicies": "[\"Default Policy\"]"
        }
      }

[borispopicbusiness]

Dockerfile has been added. Now we can built our customized Keycloak docker container. However, importing realm is still a manual process. I have lost my mind researching different versions of Keycloak. I've spent a lot of time researching various versions of Keycloak and need a day or two to take a break and clear my mind. Tomorrow, I will be researching Keycloak-backend stability with realm import still performed manually.

[borispopicbusiness]

The issue with --import-realm has been resolved. I am now testing the image and preparing to establish a connection with the PostgreSQL database intended for Keycloak's instance.

[borispopicbusiness]

ROLE_ prefix fixed in application/src/main/java/com/semiramide/timetracker/application/config/SecurityConfig.java
This issue may appear again, since Keycloak has been upgraded. Then, 404 error has been fixed. That has to be tested. The urls. Anyway, Backend is runnable again, but i have to check if it is fully functional again.

See commit 76569f8

[borispopicbusiness]

bash script for testing keycloak flow added, role assigned, user created/updated/deleted. the flow works
README.md updated