libre.sh/keycloak-scim
2
0
Fork 0
Code Issues 14 Pull requests Releases Packages Activity Actions 6

[KEYCLOAK-9809] Support private_key_jwt authentication for external IdP

Browse source
This commit is contained in:
madgaet 2019-09-14 14:22:10 +02:00 committed by Marek Posolda
parent dcc4117bd0
commit 60500036e9
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
server_admin/topics/identity-broker/oidc.adoc
View file

@ -33,6 +33,11 @@ You must define the OpenID Connect configuration options as well. They basicall
|User Info URL |User Info URL
|User Info URL endpoint defined by the OIDC protocol. This is an endpoint from which user profile information can be downloaded. |User Info URL endpoint defined by the OIDC protocol. This is an endpoint from which user profile information can be downloaded.
|Client Authentication
|Switch to define the Client Authentication method to be used with the Authorization Code Flow. In the case of JWT signed with private key, the realm private key
is used. In the other cases, a client secret has to be defined.
For more details, see the https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication[Client Authentication specifications].
|Client ID |Client ID
|This realm will act as an OIDC client to the external IDP. Your realm will need an OIDC client ID when using the Authorization Code Flow |This realm will act as an OIDC client to the external IDP. Your realm will need an OIDC client ID when using the Authorization Code Flow
to interact with the external IDP. to interact with the external IDP.