From ca367fe4d713b193f70d8a89f041246a7c1b3375 Mon Sep 17 00:00:00 2001 From: valiantlynx <86688436+valiantlynx@users.noreply.github.com> Date: Tue, 4 Aug 2026 23:27:36 +0200 Subject: [PATCH] Fix OpenID redirect URI in README Updated the OpenID sign-in redirect URI in the README. Signed-off-by: valiantlynx <86688436+valiantlynx@users.noreply.github.com> --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index f37f935..471e180 100644 --- a/README.md +++ b/README.md @@ -742,10 +742,10 @@ You can configure a Huly instance to authorize users (sign-in/sign-up) using an ### On the IdP side 1. Create a new OpenID application. - * Use `{huly_account_svc}/auth/openid/callback` as the sign-in redirect URI. The `huly_account_svc` is the hostname for the account service of the deployment, which should be accessible externally from the client/browser side. In the provided example setup, the account service runs on port 3000. + * Use `{huly_account_svc}/_accounts/auth/openid/callback` as the sign-in redirect URI. The `huly_account_svc` is the hostname for the account service of the deployment, which should be accessible externally from the client/browser side. In the provided example setup, the account service runs on port 3000. **URI Example:** - - `http://huly.mydomain.com:3000/auth/openid/callback` + - `http://huly.mydomain.com:3000/_accounts/auth/openid/callback` 2. Configure user access to the application as needed.