Changes for page 268 - Underlying Update

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-268 - Underlying Update
	1	+261 - Taking Charge

Content

...	...	@@ -1,19 +1,16 @@
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.
	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>>doc:Main.Release Information.Release Blogs.268 - Underlying Update.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		-* General - Event Streaming: Various updates regarding the proxy certificate rotation process.
8		-** 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.
9		-** If certificate rotation fails in the test environment, it will not continue to ACCP and PROD
10		-* General - Feedback Functionality: Updated the feedback functionality. Although this changes the user process, it should allow you to provide more elaborate feedback.
	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 ====
13		-
14		-* 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)
15		-* Create - Documentation Portal: A stability improvement will be rolled out for our documentation website.
16		-
17	17	==== Remarks ====
18	18
19		-* Upgraded our main application to Mendix 10
	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.