Hi @bulivlad!
Unfortunately the assigning of permissions to applications via configuration is not currently supported, we have a task on our board to move towards adding this support but I am unable to say when this will be delivered.
Although I’m not aware of your testing setup, one thought would be that the Keycloak image in the docker compose file you shared relies on an in memory database which could explain why you experience having to assign the permissions repeatedly.
An alternative is to either use a database with the current image (which will provide persistence), or use an alternative image (such as the image used in the Camunda Platform Helm charts which requires a database).
An example of the updated Keycloak service and accompanying Postgres:
postgres:
container_name: keycloak-postgres
image: postgres:14.5-alpine
environment:
POSTGRES_DB: bitnami_keycloak
POSTGRES_USER: bn_keycloak
POSTGRES_PASSWORD: <PASSWORD>
keycloak:
depends_on:
- postgres
container_name: keycloak
image: bitnami/keycloak:16.1.1
ports:
- "18080:8080"
environment:
KEYCLOAK_DATABASE_HOST: keycloak-postgres
KEYCLOAK_DATABASE_PASSWORD: <PASSWORD>
KEYCLOAK_ADMIN_USER: admin
KEYCLOAK_ADMIN_PASSWORD: admin
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:9990/health"]
interval: 30s
timeout: 15s
retries: 5
start_period: 30s
Hopefully this helps,
Ben