Skip to Content

Changes for page 261 - Taking Charge

Last modified by Erik Bakker on 2026/02/12 09:08
From version 269.2
edited by Erik Bakker
on 2025/07/14 07:12
Change comment: Update document after refactoring.
To version 309.1
edited by Erik Bakker
on 2026/02/10 09:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -249 - Amendment Avalanche
1 +261 - Taking Charge
Content
... ... @@ -1,11 +1,16 @@
1 -This release introduces the ability for beta models to run on our new event broker. With this critical step being reached, we can migrate the first set of beta customers to the new event broker while simultaneously further developing this proposition.
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.2471 - Help Out.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 -==== New features ====
5 +==== New Features ====
6 6  
7 -* General - Event Streaming: Run your event streaming solution on our new event broker at DSH. Please note that we will initially release this functionality as a **beta** feature. This means it is currently only available to a select number of models. Once this functionality is more developed, we will share more information on this.
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.
8 8  
9 -==== Minor changes ====
11 +==== Remarks ====
10 10  
11 -* Deploy - Properties: A new data type option is introduced on the property level. This data type enables the storage of PEM certificates in their correct format, which is necessary for a secure connection to DSH.
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.