From b45e90b1d437d09caa4bc4db0a29a10a969f1c51 Mon Sep 17 00:00:00 2001 From: Bogdan Carpusor Date: Wed, 30 Oct 2024 09:27:06 +0000 Subject: [PATCH] Fix unified login guide urls --- .../multiple-frontends-with-separate-backends.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/v2/unified-login/multiple-frontends-with-separate-backends.mdx b/v2/unified-login/multiple-frontends-with-separate-backends.mdx index e247335cf..5fa1a4061 100644 --- a/v2/unified-login/multiple-frontends-with-separate-backends.mdx +++ b/v2/unified-login/multiple-frontends-with-separate-backends.mdx @@ -123,8 +123,8 @@ If the creation was successful, the API will return a response that looks like t ``` Based on the client creation process we can also infer two additional values that we will need later on: -- `authorizeUrl` corresponds to `^{form_apiDomain}^{form_apiBasePath}oauth/auth` -- `tokenFetchUrl` corresponds to `^{form_apiDomain}^{form_apiBasePath}oauth/token` +- `authorizeUrl` corresponds to `^{form_apiDomain}^{form_apiBasePath}/oauth/auth` +- `tokenFetchUrl` corresponds to `^{form_apiDomain}^{form_apiBasePath}/oauth/token` :::caution