Skip to Content

Changes for page 55

Last modified by Erik Bakker on 2023/01/23 13:58
From version 15.1
edited by Erik Bakker
on 2022/06/16 13:07
Change comment: There is no comment for this version
To version 14.1
edited by Erik Bakker
on 2022/06/16 13:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -55
1 +56
Content
... ... @@ -1,25 +1,17 @@
1 -Small update that adds OAuth 2.0 resource server support and improves JSON transformations.
1 +Small update that improves platform error handling.
2 2  
3 3  Find out more in our [release blog]
4 4  
5 5  
6 -===== New Features =====
7 -
8 -* Added support for several new OAuth2 related flow designer components: Secured channels, Access decision manager, Channel security interceptor, Filter chain proxy, OAuth2 bearer token authentication filter, Authentication manager, OAuth2 JWT authentication provider.
9 -
10 10  ===== Major Changes =====
11 11  
12 -* eMagiz transformations that output JSON now automatically use the JSON data type (string, number or boolean) that best matches the data type specified in your eMagiz data model. (Previously, all attributes were written to JSON using a string representation.)
8 +* Multiple improvements to the 'Error to XML transformer' to prevent error messages from growing too large in certain circumstances, which could negatively impact performance and stability:
9 + ** Removed the 'omit stack trace' functionality: this option wasn't used in eMagiz (defaulted to 'true') and would significantly increase the size of errors by including full stack frame info (Java class names, method names, line numbers, etc).
10 + ** Message history is now truncated to 100 entries max (keeping the first and last 50). Normally message history would never reach this limit, but when building (potentially infinite) loops in eMagiz flows it was possible to create humongous 'history' headers.
11 + ** Message headers are now truncated to 40 entries max (keeping the first 40 headers alphabetically).
12 + ** XML validation errors are now truncated to 40 entries max (keeping the first 40 validation errors reported by the underlying validation engine).
13 + ** "Caused by" exception chains are now truncated to a maximum depth of 5 levels. In normal circumstances exceptions would not be expected to reach this limit, but flows with incorrectly configured custom (recursive) error handling could cause extremely long exception chains.
13 13  
14 14  ===== Minor Changes =====
15 15  
16 -* Added bundle 'com.emagiz.bundles.asm' 5.2.1
17 -* Added bundle 'com.emagiz.bundles.minidev-json' 2.3.1
18 -* Added bundle 'com.emagiz.bundles.nimbus-jose-jwt' 8.20.1.1
19 -* Added bundle 'com.emagiz.bundles.spring-integration-security' 5.2.3.1
20 -* Added bundle 'com.emagiz.bundles.spring-security-oauth2-jose' 5.3.4.1
21 -* Added bundle 'com.emagiz.bundles.spring-security-oauth2-resource-server' 5.3.4.1
22 -* Added bundle 'com.emagiz.osgi.extender.core-web' 1.0.0
23 -* Added bundle 'com.emagiz.osgi.extender.security' 1.0.0
24 -* Updated bundle 'com.emagiz.components.http' from 7.0.1 to 7.1.0
25 -* Updated bundle 'com.emagiz.components.staxon' from 1.0.0 to 1.1.0
17 +* Updated bundle 'com.emagiz.components.error' from 7.0.0 to 7.1.0