KEYCLOAK-16679 Add algorithm settings for client assertion signature in OIDC identity broker

- fix about reviewer's comments
This commit is contained in:
i7a7467 2021-02-05 01:20:34 +09:00 committed by Marek Posolda
parent ecc3176455
commit 6b16d408ee

View file

@ -47,7 +47,7 @@ You must define the OpenID Connect configuration options as well. They basicall
|Client Assertion Signature Algorithm |Client Assertion Signature Algorithm
|Signature algorithm to create JWT assertion as client authentication. |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 |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. |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.