Changes for page 262 - Good News

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-261 - Taking Charge
	1	+199 - Home Improvements

Content

...	...	@@ -1,16 +1,20 @@
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.
	1	+In the last sprint cycle we have focused on improving various aspects of the portal functionality. Among others we focused on the next-generation architecture, the store, security and certificate management.
2	2
3		-Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.261 - Taking Charge.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.199 - Home Improvements.WebHome||target= "blank"]].
4	4
5		-==== New Features ====
	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	+* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately 3 months before the expiration dates of event streaming users' access certificates.
	8	+* Deploy - Release: After successful machine deployments, unused runtime images will be automatically removed. This can be disabled by changing the machine step in your deployment plan.
	9	+* Manage - Monitoring: HTTP statistics page now displays all of the resources.
	10	+* Manage - Alerting: congestion control wil be enabled by default with 10 alerts per 10 minutes and user cannot see or change it.
	11	+* General - Infra: Changed the library used for storing metadata in the eMagiz Control Tower.
10	10
11		-==== Remarks ====
	13	+====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.
	15	+* Create - Store: Spring Reserved words that contain * are not incorrectly replaced with the prefix of the flow.
	16	+* Manage - Monitoring: When an application failed to start, not all log messages were visible in the manage phase.
	17	+
	18	+====Remarks====
	19	+
	20	+* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.