From 5d3294bf286034eb633ecf8d27020625a1d99120 Mon Sep 17 00:00:00 2001 From: Sarma <131+amras@noreply.git.coopcloud.tech> Date: Fri, 6 Nov 2026 11:19:08 +0000 Subject: [PATCH] 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> --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index f000f9f..41dee27 100644 --- a/README.md +++ b/README.md @@ -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:///api/v1.0/callback/` (don't forget the trailing slash) + - Home URL: `https:///` + - Root URL: `https:///` * 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 oidc_rpcs v2 ` * `abra app config ` # set SECRET_OIDC_RPCS_VERSION=v2