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

Fix typos in V7.0 document

Browse source
This commit is contained in:
k-tamura 2019-09-18 13:34:17 +09:00 committed by Stian Thorgersen
parent cd7309ddaf
commit c8028638c8
4 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
securing_apps/topics/oidc/java/jboss-adapter-rpms.adoc
View file

@ -33,7 +33,7 @@ Install the {appserver_name} 7 adapters for OIDC using the following command at
$ sudo yum install eap7-keycloak-adapter-sso7_3 $ sudo yum install eap7-keycloak-adapter-sso7_3
---- ----
or use following one for Red Hat Red Hat Enterprise Linux 8: or use following one for Red Hat Enterprise Linux 8:
---- ----
$ sudo dnf install eap7-keycloak-adapter-sso7_3 $ sudo dnf install eap7-keycloak-adapter-sso7_3

2
securing_apps/topics/saml/java/jboss-adapter/jboss-adapter-rpms.adoc
View file

@ -33,7 +33,7 @@ Install the EAP 7 adapters for SAML using the following command:
$ sudo yum install eap7-keycloak-saml-adapter-sso7_3 $ sudo yum install eap7-keycloak-saml-adapter-sso7_3
---- ----
or use following one for Red Hat Red Hat Enterprise Linux 8: or use following one for Red Hat Enterprise Linux 8:
---- ----
$ sudo dnf install eap7-keycloak-adapter-sso7_3 $ sudo dnf install eap7-keycloak-adapter-sso7_3

2
server_admin/topics/authentication/x509.adoc
View file

@ -172,7 +172,7 @@ Defines how to extract the user identity from a client certificate.
Defines whether to use the canonical format to determine a distinguished name. Defines whether to use the canonical format to determine a distinguished name.
The format is described in detail in the official link:https://docs.oracle.com/javase/8/docs/api/javax/security/auth/x500/X500Principal.html#getName-java.lang.String-[Java API documentation] . The format is described in detail in the official link:https://docs.oracle.com/javase/8/docs/api/javax/security/auth/x500/X500Principal.html#getName-java.lang.String-[Java API documentation] .
This option only affects the two User Identity Sources _Match SubjectDN using regular expression_ and _Match IssuerDN using regular expression_. This option only affects the two User Identity Sources _Match SubjectDN using regular expression_ and _Match IssuerDN using regular expression_.
If you setup a new keycloak instance it is recommended to enable this option. Leave this option disabled to remain beckward compatible with existing Keycloak instances. If you setup a new {project_name} instance it is recommended to enable this option. Leave this option disabled to remain beckward compatible with existing {project_name} instances.
`Enable Serial Number hexadecimal representation` (optional):: `Enable Serial Number hexadecimal representation` (optional)::
An option to use hexadecimal representation of the Serial Number. See link:https://tools.ietf.org/html/rfc5280#section-4.1.2.2[RFC5280, Section-4.1.2.2]. Serial Number with sign bit set to 1 should be left padded with 00 octet. E.g. Serial number with decimal value _161_, or _a1_ in hexadecimal representation according to RFC5280 must be encoded as _00a1_. More details can be found: link:https://tools.ietf.org/html/rfc5280#appendix-B[RFC5280, appendix-B]. An option to use hexadecimal representation of the Serial Number. See link:https://tools.ietf.org/html/rfc5280#section-4.1.2.2[RFC5280, Section-4.1.2.2]. Serial Number with sign bit set to 1 should be left padded with 00 octet. E.g. Serial number with decimal value _161_, or _a1_ in hexadecimal representation according to RFC5280 must be encoded as _00a1_. More details can be found: link:https://tools.ietf.org/html/rfc5280#appendix-B[RFC5280, appendix-B].

2
server_admin/topics/clients/client-oidc.adoc
View file

@ -157,7 +157,7 @@ The administrator can select the following three options:
*Proof Key for Code Exchange Code Challenge Method* *Proof Key for Code Exchange Code Challenge Method*
* (blank) : {project_name} does not apply PKCE unless the client sends PKCE's parameters appropriately to keycloak's authorization endpoint. It is the default setting. * (blank) : {project_name} does not apply PKCE unless the client sends PKCE's parameters appropriately to {project_name}'s authorization endpoint. It is the default setting.
* S256 : {project_name} applies to the client PKCE whose code challenge method is S256. * S256 : {project_name} applies to the client PKCE whose code challenge method is S256.
* plain : {project_name} applies to the client PKCE whose code challenge method is plain. * plain : {project_name} applies to the client PKCE whose code challenge method is plain.