Compare commits

..
Author SHA1 Message Date
Linus Gasser 5d96080eee chore: publish 0.9.0+v1.37.0 release 2026-11-12 18:05:18 +01:00
Linus Gasser d475c5c2d1 chore: update image tags 2026-11-12 18:01:14 +01:00
Sarma 5d3294bf28 Update Authentication docs for URI config
When I follow the instructions but *don't* specify the Redirect URI - and then go to my Meet domain, I just get an error that the redirect uri is invalid.

Also moved Client authentication higher up to match the layout of keycloak's UI.

Signed-off-by: Sarma <131+amras@noreply.git.coopcloud.tech>
2026-11-06 11:19:08 +00:00
Linus Gasser fbcfda0da3 chore: publish 0.8.2+v1.36.3 release 2026-10-28 16:38:54 +01:00
Renovate Bot ced81cce4f chore(deps): update redis docker tag to v8.10.3 2026-10-28 15:38:04 +00:00
Renovate Bot 35abe91b39 chore(deps): update livekit/livekit-server docker tag to v1.13.11 2026-10-28 15:37:55 +00:00
Renovate Bot 318fa5415a chore(deps): update lasuite/meet-frontend docker tag to v1.36.3 2026-10-28 15:37:47 +00:00
Renovate Bot 6a2ff629f0 chore(deps): update lasuite/meet-backend docker tag to v1.36.3 2026-10-26 17:15:43 +00:00
notplants 9789595384 chore: publish 0.8.1+v1.36.2 release 2026-10-26 12:29:28 -04:00
cc-ci e44a00a00e chore: upgrade to 1.36.2 (meet v1.36.0 -> v1.36.2, nginx 1.31.7 -> 1.31.8)
cc-ci/testme cc-ci: success
2026-10-23 03:37:37 +00:00
3 changed files with 12 additions and 8 deletions
+4 -1
View File
@@ -39,11 +39,14 @@ Instructions for integrating keycloak with meet after deploying it, are below.
* In keycloak, create a realm (save the name of this realm, you will need it later)
* Within that realm, create a client
* during client creation, ensure:
- Client authentication: True
- Standard flow: True
- Direct access grants: True
- Authorization: True
- Client authentication: True
- PKCE method: none
- Valid Redirect URIs: `https://<your-meet-domain>/api/v1.0/callback/` (don't forget the trailing slash)
- Home URL: `https://<your-meet-domain>/`
- Root URL: `https://<your-meet-domain>/`
* Within the client tab, for your client, click on "Credentials". Click on the copy button to copy "Client Secret" so you can insert this into your coop cloud deployment in the next step.
* `abra app secret insert <app-name> oidc_rpcs v2 <yoursecret>`
* `abra app config <app-name>` # set SECRET_OIDC_RPCS_VERSION=v2
+7 -7
View File
@@ -64,14 +64,14 @@ x-postgres-env: &postgres-env
services:
app:
image: lasuite/meet-frontend:v1.36.0
image: lasuite/meet-frontend:v1.37.0
networks:
- backend
deploy:
labels:
- "traefik.enable=false"
- "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT:-120}"
- "coop-cloud.${STACK_NAME}.version=0.8.0+v1.36.0"
- "coop-cloud.${STACK_NAME}.version=0.9.0+v1.37.0"
user: "${DOCKER_USER:-1000}"
entrypoint:
- /docker-entrypoint.sh
@@ -87,7 +87,7 @@ services:
start_period: 10s
backend:
image: lasuite/meet-backend:v1.36.0
image: lasuite/meet-backend:v1.37.0
networks:
- backend
environment:
@@ -119,7 +119,7 @@ services:
- email_pass
celery:
image: lasuite/meet-backend:v1.36.0
image: lasuite/meet-backend:v1.37.0
networks:
- backend
healthcheck:
@@ -173,7 +173,7 @@ services:
- postgres_p
redis:
image: redis:8.10.2
image: redis:8.10.3
healthcheck:
test: ["CMD", "redis-cli", "ping"]
interval: 15s
@@ -183,7 +183,7 @@ services:
- backend
livekit:
image: livekit/livekit-server:v1.13.10
image: livekit/livekit-server:v1.13.11
command: --config /livekit-server.yaml
environment:
- STACK_NAME
@@ -223,7 +223,7 @@ services:
- "traefik.http.services.${STACK_NAME}_livekit.loadbalancer.server.port=7880"
web:
image: nginx:1.31.7
image: nginx:1.31.8
environment:
- STACK_NAME
healthcheck:
+1
View File
@@ -0,0 +1 @@
Latest security updates