Changes for page 268 - Underlying Update
Last modified by Erik Bakker on 2026/05/18 16:45
From version 310.1
edited by Erik Bakker
on 2026/02/10 09:01
on 2026/02/10 09:01
Change comment:
There is no comment for this version
To version 336.1
edited by Erik Bakker
on 2026/05/18 16:45
on 2026/05/18 16:45
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -26 1-TakingCharge1 +268 - Underlying Update - Content
-
... ... @@ -1,16 +1,18 @@ 1 -This release includes a lot ofupdatesto ourplatform. Wearereleasingsomebetafeaturesforcustomersutilizing ourlatestversionoftheAPIGatewayallowing to usemultipleauthenticationmethods. On top of thatwe willreleasea newenvironmenttemplatethatwillupdateamultitudeof configurations oncloud andon-premisemachines.Furthermore, wehave aseriesofsmallerimprovementstobringdelight to your everydaywork.1 +This release includes significant improvements regarding our internal platforms. This includes improvements in the DSH proxy certificate rotation process. On top of that, it introduces a new version of Mendix on which we are running, as well as various updates to underlying libraries. Subsequently, we introduced a fix to improve the stability of our documentation platform. Enjoy reading our latest updates on the platform. 2 2 3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.26 1-TakingCharge.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.268 - Underlying Update.WebHome||target="blank"]]. 4 4 5 -==== NewFeatures ====5 +==== Minor Changes ==== 6 6 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. 7 +* General - Platform: As part of our regular system maintenance, we have upgraded the application to the Mendix LTS version 10.24. 8 +** This upgrade improves overall stability, security, and long-term reliability of the platform. There is no impact on daily operations. 9 +** This update ensures the application remains well-supported and ready for future enhancements. 10 +* General - Event Streaming: Various updates regarding the proxy certificate rotation process. 11 +** Proxy certificates must always be valid in DSH to prevent clients from encountering issues. A scheduled event runs daily during working hours to verify this. 12 +** If certificate rotation fails in the test environment, it will not continue to ACCP and PROD 13 +* General - Feedback Functionality: Updated the feedback functionality. Although this changes the user process, it should allow you to provide more elaborate feedback. 10 10 11 -==== Remarks ====15 +==== Bug fixes ==== 12 12 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. 17 +* General - User Access Control: While users are being deactivated, they are also being removed from the models unless they are the contact person for the model. (#943) 18 +* Create - Documentation Portal: A stability improvement will be rolled out for our documentation website.