From 4c9729290dfbac8fdb0b3ee189c12379133ecd76 Mon Sep 17 00:00:00 2001 From: si458 Date: Tue, 30 Sep 2025 17:09:40 +0100 Subject: [PATCH] fix response_types example in oidc docs Signed-off-by: si458 --- docs/docs/meshcentral/openidConnectStrategy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/meshcentral/openidConnectStrategy.md b/docs/docs/meshcentral/openidConnectStrategy.md index 35162879..b442267c 100644 --- a/docs/docs/meshcentral/openidConnectStrategy.md +++ b/docs/docs/meshcentral/openidConnectStrategy.md @@ -130,7 +130,7 @@ There are plenty of options at your disposal if you need them. In fact, you can "redirect_uri": "https://mesh.your.domain/auth-oidc-callback", "post_logout_redirect_uri": "https://mesh.your.domain/login", "token_endpoint_auth_method": "client_secret_post", - "response_types": "authorization_code" + "response_types": "code" }, "custom": { "scope": [ "openid", "profile", "read.EmailAlias", "read.UserProfile" ], @@ -256,7 +256,7 @@ There are just about as many option as possible here since openid-client also pr "redirect_uri": "https://mesh.your.domain/auth-oidc-callback", "post_logout_redirect_uri": "https://mesh.your.domain/login", "token_endpoint_auth_method": "client_secret_post", - "response_types": "authorization_code" + "response_types": "code" }, ```