libre.sh/keycloak-scim
4
0
Fork 0
Code Issues 15 Pull requests Releases 1 Activity Actions

KEYCLOAK-9509 Upgrade to WildFly 15

Browse source
This commit is contained in:
Hynek Mlnarik 2019-02-22 15:35:18 +01:00 committed by Stian Thorgersen
parent 862b8eb77e
commit 8abf3d3226
5 changed files with 28 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -140,7 +140,7 @@ See details https://github.com/mposolda/keycloak-freeipa-docker/blob/master/READ
For quick testing and unit tests, we use a very simple http://directory.apache.org/apacheds/[ApacheDS] Kerberos server.
You need to build {project_name} from sources and then run the Kerberos server with maven-exec-plugin from our testsuite.
See details https://github.com/keycloak/keycloak/blob/master/misc/Testsuite.md#user-content-kerberos-server[here] .
See details https://github.com/keycloak/keycloak/blob/master/docs/tests.md#kerberos-server[here] .
endif::[]
==== Credential Delegation

6
server_installation/topics/operating-mode/crossdc.adoc
View file

@ -24,8 +24,8 @@ As this is an advanced topic, we recommend you first read the following, which p
When setting up for Cross-Datacenter Replication, you will use more independent {project_name} clusters, so you must understand how a cluster works and the basic concepts and requirements such as load balancing, shared databases, and multicasting.
* link:{jdgserver_crossdcdocs_link}[JBoss Data Grid Cross-Datacenter Replication]
{project_name} uses JBoss Data Grid (JDG) for the replication of Infinispan data between the data centers. We use the `Remote Client-Server Mode`
described in the JDG documentation in link:{jdgserver_crossdcdocs_link}#configure_cross_datacenter_replication_remote_client_server_mode[Configure Cross-Datacenter Replication].
{project_name} uses JBoss Data Grid (JDG) for the replication of Infinispan data between the data centers.
[[technicaldetails]]
@ -151,7 +151,7 @@ For this example, we describe using two data centers, `site1` and `site2`. Each
* `Site2` consists of {jdgserver_name} server, `jdg2`, and 2 {project_name} servers, `node21` and `node22` .
* {jdgserver_name} servers `jdg1` and `jdg2` are connected to each other through the RELAY2 protocol and `backup` based {jdgserver_name}
caches in a similar way as described in the link:{jdgserver_crossdcdocs_link}#configure_cross_datacenter_replication_remote_client_server_mode[JDG documentation].
caches in a similar way as described in the link:{jdgserver_crossdcdocs_link}[JDG documentation].
* {project_name} servers `node11` and `node12` form a cluster with each other, but they do not communicate directly with any server in `site2`.
They communicate with the Infinispan server `jdg1` using the HotRod protocol (Remote cache). See <<communication>> for the details.

8
topics/templates/document-attributes-community.adoc
View file

@ -67,9 +67,9 @@
:appserver_name: WildFly
:appserver_dirref: WILDFLY_HOME
:appserver_version: 13
:appserver_version: 15
:appserver_doc_base_url: http://docs.wildfly.org/13
:appserver_doc_base_url: http://docs.wildfly.org/15
:appserver_socket_link: {appserver_doc_base_url}/Admin_Guide.html#Interfaces_and_ports
:appserver_socket_name: {appserver_name} {appserver_version} Documentation
:appserver_jgroups_link: {appserver_doc_base_url}/High_Availability_Guide.html#JGroups_Subsystem
@ -88,8 +88,8 @@
:appserver_loadbalancer_name: {appserver_name} {appserver_version} Documentation
:jdgserver_name: Infinispan
:jdgserver_version: 9.3.1
:jdgserver_crossdcdocs_link: https://access.redhat.com/documentation/en-us/red_hat_data_grid/7.2/html/administration_and_configuration_guide/set_up_cross_datacenter_replication
:jdgserver_version: 9.4.3
:jdgserver_crossdcdocs_link: https://access.redhat.com/documentation/en-us/red_hat_data_grid/7.3/html/red_hat_data_grid_user_guide/x_site_replication
:fuseVersion: JBoss Fuse 6.3.0 Rollup 5
:fuseHawtioEAPVersion: JBoss EAP 6.4

4
topics/templates/document-attributes-product.adoc
View file

@ -110,8 +110,8 @@ endif::[]
:appserver_managementconsole_link: https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/html-single/configuration_guide/#management_console_overview
:jdgserver_name: JDG
:jdgserver_version: 7.2.3
:jdgserver_crossdcdocs_link: https://access.redhat.com/documentation/en-us/red_hat_data_grid/7.2/html/administration_and_configuration_guide/set_up_cross_datacenter_replication
:jdgserver_version: 7.3.0
:jdgserver_crossdcdocs_link: https://access.redhat.com/documentation/en-us/red_hat_data_grid/7.3/html/red_hat_data_grid_user_guide/x_site_replication
:fuseVersion: JBoss Fuse 6.3.0 Rollup 10
:fuseHawtioEAPVersion: JBoss EAP 6.4

18
upgrading/topics/keycloak/changes.adoc
View file

@ -1,5 +1,23 @@
== Migration Changes
=== Migrating to 5.0.0
==== Upgrade to Wildfly 15
The {project_name} server was upgraded to use Wildfly 15 as the underlying container. This does not directly involve any
specific {project_name} server functionality, but there are few changes related to the migration, which worth mentioning.
Dependency updates::
The dependencies were updated to the versions used by Wildfly 14 server. For example, Infinispan is now 9.4.3.Final.
Configuration changes::
There are few configuration changes in the `standalone(-ha).xml` and `domain.xml` files. You should follow the <<_install_new_version>>
section to handle the migration of configuration files automatically.
Cross-Datacenter Replication changes::
* You will need to upgrade {jdgserver_name} server to version {jdgserver_version}. The older version may still work, but it is
not guaranteed as we don't test it anymore.
=== Migrating to 4.8.2
==== Google Identity Provider updated to use Google Sign-in authentication system