tiran133

In case someone needs this still. You need to build your own docker image with either `ENV VITE_APP_WS_SERVER_URL=http://127.0.0.1:3002` the Dockerfile OR change it in `.env.production` This is how i did...

Since the docker compose file exposes the ports to the host via the ports section. So there are available on localhost and on the host IP ```yaml ports: - "3000:80"...

No this should be fine as long as you only change the first part of the port in the composer file ```yaml ports: - "10000:80" ``` If you want to...

I did the same in my project and it works fine. I extend my fragment as follow SlidingMenuListFragment extends SherlockListFragment I'm using the sherlockactionbar So i extend SherlockListFragment and not...

Is there any update on this? Since Keycloak 24 is released which has the user profile enabled by default.

Any update on this. I have the same issue

Hi, I manage the installation from @christophwolff and wanted to add some more information and to clear things up. > So your expectation is that a user with Drives.Create permission...

I don't see how this is a feature request. You're allowed to create your own roles using the bundles.json. I don't need this role baked into the source code. Why...

You need to import the keycloak_generic_protocol_mapper.saml_role_attribute_mapper first. https://registry.terraform.io/providers/keycloak/keycloak/latest/docs/resources/generic_protocol_mapper#import ```bash {{realm_id}}/client/{{client_keycloak_id}}/{{protocol_mapper_id}} {{realm_id}}/client-scope/{{client_scope_keycloak_id}}/{{protocol_mapper_id}} terraform import keycloak_generic_protocol_mapper.saml_role_attribute_mappermy-realm/client-scope/a7202154-8793-4656-b655-1dd18c181e14/71602afa-f7d1-4788-8c49-ef8fd00af0f4 ```

Would be nice to have this added.