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

re-added wildfly mention changes

Browse source
This commit is contained in:
Matthew Helmke 2019-01-21 12:02:18 -06:00 committed by Hynek Mlnařík
parent 2c2c7f7b50
commit 9d97b00073
2 changed files with 8 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
securing_apps/topics/saml/java/jboss-adapter/jboss_adapter_installation.adoc
View file

@ -26,6 +26,8 @@ Install on JBoss EAP 6.x:
$ cd $JBOSS_HOME $ cd $JBOSS_HOME
$ unzip keycloak-saml-eap6-adapter-dist.zip $ unzip keycloak-saml-eap6-adapter-dist.zip
---- ----
These zip files create new JBoss Modules specific to the WildFly/JBoss EAP SAML Adapter within your WildFly or JBoss EAP distro.
endif::[] endif::[]
ifeval::[{project_product}==true] ifeval::[{project_product}==true]
@ -44,11 +46,11 @@ Install on JBoss EAP 6.x:
$ cd $EAP_HOME $ cd $EAP_HOME
$ unzip rh-sso-saml-eap6-adapter.zip $ unzip rh-sso-saml-eap6-adapter.zip
---- ----
These zip files create new JBoss Modules specific to the JBoss EAP SAML Adapter within your JBoss EAP distro.
endif::[] endif::[]
These zip files create new JBoss Modules specific to the WildFly/JBoss EAP SAML Adapter within your WildFly or JBoss EAP distro.
After adding the modules, you must then enable the {project_name} SAML Subsystem within your app server's server configuration: `domain.xml` or `standalone.xml`. After adding the modules, you must then enable the {project_name} SAML Subsystem within your app server's server configuration: `domain.xml` or `standalone.xml`.
There is a CLI script that will help you modify your server configuration. There is a CLI script that will help you modify your server configuration.

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

@ -8,7 +8,7 @@ A typical workflow is as follows:
- A client sends an authentication request over SSL/TLS channel - A client sends an authentication request over SSL/TLS channel
- During SSL/TLS handshake, the server and the client exchange their x.509/v3 certificates - During SSL/TLS handshake, the server and the client exchange their x.509/v3 certificates
- The container (WildFly) validates the certificate PKIX path and the certificate expiration - The container ({appserver_name}) validates the certificate PKIX path and the certificate expiration
- The x.509 client certificate authenticator validates the client certificate as follows: - The x.509 client certificate authenticator validates the client certificate as follows:
* Optionally checks the certificate revocation status using CRL and/or CRL Distribution Points * Optionally checks the certificate revocation status using CRL and/or CRL Distribution Points
* Optionally checks the Certificate revocation status using OCSP (Online Certificate Status Protocol) * Optionally checks the Certificate revocation status using OCSP (Online Certificate Status Protocol)
@ -54,11 +54,11 @@ Other Features: Extended Certificate Validation::
==== Enable X.509 Client Certificate User Authentication ==== Enable X.509 Client Certificate User Authentication
The following sections describe how to configure WildFly/Undertow and the {project_name} Server to enable X.509 client certificate authentication. The following sections describe how to configure {appserver_name}/Undertow and the {project_name} Server to enable X.509 client certificate authentication.
[[_enable-mtls-wildfly]] [[_enable-mtls-wildfly]]
Enable mutual SSL in WildFly:: Enable mutual SSL in {appserver_name}::
See link:https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide-EnableSSL[Enable SSL] and link:https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide-%7B%7B%3Cssl%2F%3E%7D%7D[SSL] for the instructions how to enable SSL in WildFly. See link:https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide-EnableSSL[Enable SSL] and link:https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide-%7B%7B%3Cssl%2F%3E%7D%7D[SSL] for the instructions how to enable SSL in {appserver_name}.
* Open {project_dirref}/standalone/configuration/standalone.xml and add a new realm: * Open {project_dirref}/standalone/configuration/standalone.xml and add a new realm:
```xml ```xml