Changes for page 261 - Taking Charge

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-246 - Preparation Paradise
	1	+261 - Taking Charge

Content

...	...	@@ -1,17 +1,16 @@
1		-In our previous release, we released functionality to increase the stability of Windows runtimes. This time, we followed that up by adding additional safety measures on the runtime level. Additionally, we have several pieces now available to prepare for pending changes to our event streaming offering. Furthermore, we introduced several minor improvements to the platform.
	1	+This release includes a lot of updates to our platform. We are releasing some beta features for customers utilizing our latest version of the API Gateway allowing to use multiple authentication methods. On top of that we will release a new environment template that will update a multitude of configurations on cloud and on-premise machines. Furthermore, we have a series of smaller improvements to bring delight to your everyday work.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.246 - Preparation Paradise.WebHome||target= "blank"]].
	3	+Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.261 - Taking Charge.WebHome||target="blank"]].
4	4
5		-====Minor Changes====
	5	+==== New Features ====
6	6
7		-* Deploy - General: Updated the Java arguments applied to Windows containers to align with the container limits, thereby improving the stability of these containers.
8		-* General - Runtime: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V331.WebHome||target="blank"]] is available.
9		-** This adds support for consuming Kafka topics based on a ‘topics’ pattern instead of a fixed list of topic names.
10		-** This updates our Java runtime version from Java 17.0.13 to Java 17.0.15. This is primarily a security update.
	7	+* API gateways using the latest Multiple Authentication Methods feature can now configure the [[Authorization Code OAuth2 grant type>>https://auth0.com/docs/get-started/authentication-and-authorization-flow/authorization-code-flow||target="blank"]] for their gateway users. Note that the following timeouts apply:
	8	+** The authorization code is valid for **5 minutes**, meaning it should be used to obtain an access token within that period.
	9	+** Clients that obtain an access token with authorization code will also obtain a ~~refresh token~~, that can be used to obtain a subsequent access token without user intervention. This refresh token is valid for *24 hours*, meaning that the client application has to call the eMagiz API gateway at least that often, otherwise manual intervention is needed to authorize the call again.
11	11
12		-====Bug fixes====
	11	+==== Remarks ====
13	13
14		-* Create - Flow designer: We have fixed a bug where you could not add a new entry flow to a ‘SOAP Entry Connector’ enabled system.
15		-* Manage - Error Messages: The non-working download button for payload content files now displays a more descriptive error message text. (#886)
16		-* Manage - Explore (Queue Browser): Updated styling for the action buttons related to the debug functionality. (#1653)
17		-* Q&A Forum - General: You will no longer receive an email notification about your comments on posts in the Q&A forum. (#1462)
	13	+* The advised Docker version for on-premises deployments has been updated from 24.0.7 to 29.1.3. Documentation on how to update Docker can be found at:
	14	+** [[Linux>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-linux-installguide.WebHome||target="blank"]]
	15	+** [[Windows>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-windows-installguide.WebHome||target="blank"]]
	16	+* An infrastructure change has been applied to the container registry to improve how traffic is managed within our own environment.