Skip to Content

Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/04/18 13:04
From version 419.1
edited by Erik Bakker
on 2024/03/11 15:19
Change comment: There is no comment for this version
To version 423.1
edited by Erik Bakker
on 2024/03/12 14:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,16 +7,19 @@
7 7  
8 8  == ** Announcement - TLS versions deprecated** ==
9 9  
10 -Placeholder for info from Bas
10 +As eMagiz, we continuously validate our best practices configuration on security to the industry-wide standards in the fields of security to uphold our reputation as a reliable and secure integration platform. As a result of our latest evaluation, we decided to follow the industry-wide standard to **not** support the following TLS versions anymore in our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3.WebHome||target="blank"]]** architecture for outgoing connections from eMagiz to external systems as of April 11th, 2024.
11 11  
12 +* TLSv1.0
13 +* TLSv1.1
14 +
12 12  {{info}}Text{{/info}}
13 13  
14 14  == **Announcement - Spring 6** ==
15 15  
16 -We expect to release a major version of our current runtime base image for all our clients running on the **current runtime** architecture in the next release. This image moves the eMagiz stack from Java 8 to Java 17 and from Spring Framework 5 to Spring Framework 6. Although eMagiz will try to make the transition as smooth as possible, we recommend that you start with the following preparations.
19 +We will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3.WebHome||target="blank"]] base image for all our clients running on the **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3.WebHome||target="blank"]]** architecture in our release that will be released on April 11th, 2024. This image moves the eMagiz stack from Java 8 to Java 17 and from Spring Framework 5 to Spring Framework 6. Although eMagiz will try to make the transition as smooth as possible, we recommend that you start with the following preparations.
17 17  
18 18  {{warning}}
19 -* Make sure that your release is running on the **latest** flow versions. After the release of the new image, eMagiz will push new flow versions of components that have changed. These new flow versions must be included in the subsequent release. Having your release already on the **latest** flow versions makes this less affecting
22 +* Make sure that your release is running on the **latest** flow versions. After the release of the new image, eMagiz will push new flow versions of components that have changed. These new flow versions must be included in the subsequent release. Having your release already on the **latest** flow versions makes this less affecting.
20 20  * To help you identify which flow versions are essential here, you can consider all flows that contain any of the following components:
21 21  ** Simple job launcher (data pipelines)
22 22  ** Job explorer (data pipelines)
... ... @@ -25,7 +25,7 @@
25 25  ** SFTP session factory (support object)
26 26  ** API gateways with OAuth2 as security mechanism.
27 27  * We recommend identifying flows with (advanced) custom Groovy scripts. As our Java and Spring versions change, this may affect the availability of the libraries on the classpath and, therefore, the validity of import statements. You can already test the Groovy script using the flow testing functionality, as flow testing is already running on the Java 17 and Spring Framework 6 baseline.
28 -** Additionally, the Groovy version has been moved from 3.0.19 to 4.0.18. These changes may affect your scripts as well. The release notes of the base image will specify the changes in more detail.
31 +** Additionally, the Groovy version has been moved from 3.0.19 to 4.0.18. These changes may affect your scripts as well. [[These release notes >>https://groovy-lang.org/releasenotes/groovy-4.0.html||target="blank"]] will specify the changes in more detail.
29 29  * The code handling SFTP file transfer has been overhauled completely. Although this should not affect you, we encourage you to test your SFTP integrations before deploying to Production. {{/warning}}
30 30  
31 31  == **Infra flow selection** ==