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

Fix an incorrect image title and typos

Browse source
This commit is contained in:
Kohei Tamura 2019-04-13 23:07:33 +09:00 committed by Stian Thorgersen
parent 4b8cd16ac6
commit d6eb802a66
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
server_admin/topics/clients/oidc/confidential.adoc
View file

@ -39,8 +39,8 @@ There are multiple formats you can import from, just choose the archive format y
select the file, and click the `Import` button.
Finally note that you don't even need to import certificate if you choose to `Use JWKS URL` . In that case, you can provide the URL where
client publishes it's public key in https://self-issued.info/docs/draft-ietf-jose-json-web-key.html[JWK] format. This is flexible because when
client changes it's keys, {project_name} will automatically download them without need to re-import anything on {project_name} side.
client publishes its public key in https://self-issued.info/docs/draft-ietf-jose-json-web-key.html[JWK] format. This is flexible because when
client changes its keys, {project_name} will automatically download them without need to re-import anything on {project_name} side.
If you use client secured by {project_name} adapter, you can configure the JWKS URL like https://myhost.com/myapp/k_jwks assuming that https://myhost.com/myapp is the
root URL of your client application. See link:{developerguide_link}[{developerguide_name}] for additional details.
@ -61,7 +61,7 @@ By enabling this option {project_name} will validate if the client uses proper X
NOTE: This option requires mutual TLS in {project_name}, see <<_enable-mtls-wildfly, Enable mutual SSL in WildFly>>.
.Import Certificate
.X509 Certificate
image:{project_images}/x509-client-auth.png[]
The validator checks also the certificate's Subject DN field with configured regexp validation expression. For some