From 6b16d408eebb3144e859d5c37620d18d55d48d22 Mon Sep 17 00:00:00 2001 From: i7a7467 Date: Fri, 5 Feb 2021 01:20:34 +0900 Subject: [PATCH] KEYCLOAK-16679 Add algorithm settings for client assertion signature in OIDC identity broker - fix about reviewer's comments --- server_admin/topics/identity-broker/oidc.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server_admin/topics/identity-broker/oidc.adoc b/server_admin/topics/identity-broker/oidc.adoc index 52a3d8ed9b..4f144211a6 100644 --- a/server_admin/topics/identity-broker/oidc.adoc +++ b/server_admin/topics/identity-broker/oidc.adoc @@ -47,7 +47,7 @@ You must define the OpenID Connect configuration options as well. They basicall |Client Assertion Signature Algorithm |Signature algorithm to create JWT assertion as client authentication. -In the case of JWT signed with private key or Client secret as jwt, it is required. If no algorithm is specified, the following algorithm is adapted. `RS256` is adapted the in the case of JWT signed with private key. `HS256` is adapted the in the case of Client secret as jwt. +In the case of JWT signed with private key or Client secret as jwt, it is required. If no algorithm is specified, the following algorithm is adapted. `RS256` is adapted in the case of JWT signed with private key. `HS256` is adapted in the case of Client secret as jwt. |Issuer |Responses from the IDP may contain an issuer claim. This config value is optional. If specified, this claim will be validated against the value you provide.