Skip to Content

Changes for page 55

Last modified by Erik Bakker on 2023/01/23 13:58
From version 9.1
edited by Erik Bakker
on 2022/06/16 12:48
Change comment: There is no comment for this version
To version 16.1
edited by Erik Bakker
on 2023/01/23 13:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -60
1 +55
Content
... ... @@ -1,14 +1,22 @@
1 -Small update that fixes three specific issues.
1 +Small update that adds OAuth 2.0 resource server support and improves JSON transformations.
2 2  
3 -Find out more in our [release blog]
3 +===== New Features =====
4 4  
5 +* 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.
5 5  
6 -===== Bug Fixes =====
7 +===== Major Changes =====
7 7  
8 -* Build number 59 broke the debugger, build number 60 fixes this.
9 -* Fixed Kafka components not being able to use key- or truststores from the "resources" tab.
10 -* Deploying flows containing a 'Jetty server' support object in build number 59 only worked on the latest runtime version: build number 60 fixes the backwards compatibility with older runtimes. Note that it is still strongly recommended to update to the latest version of the runtime (5.0.4) if you haven't done so already, because this contains fixes for the Log4j security vulnerability.
9 +* 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.)
11 11  
12 12  ===== Minor Changes =====
13 13  
14 -* Change of behaviour when incoming HTTP headers are mapped to message headers: Up to build 58 the values of incoming HTTP headers were only mapped to an array when it contained multiple values, otherwise the first (and only) value was automatically extracted and used for the message header. Since build 59 the values are always mapped to an array. While this makes the data type of the header more predictable - it is no longer dependent on the number of values a client was sending - it does mean that your SpEL expressions that were previously expecting single values need to now handle array values. In many cases this can be as simple as extracting the first array value like this: "headers.myHeader[0]".
13 +* Added bundle 'com.emagiz.bundles.asm' 5.2.1
14 +* Added bundle 'com.emagiz.bundles.minidev-json' 2.3.1
15 +* Added bundle 'com.emagiz.bundles.nimbus-jose-jwt' 8.20.1.1
16 +* Added bundle 'com.emagiz.bundles.spring-integration-security' 5.2.3.1
17 +* Added bundle 'com.emagiz.bundles.spring-security-oauth2-jose' 5.3.4.1
18 +* Added bundle 'com.emagiz.bundles.spring-security-oauth2-resource-server' 5.3.4.1
19 +* Added bundle 'com.emagiz.osgi.extender.core-web' 1.0.0
20 +* Added bundle 'com.emagiz.osgi.extender.security' 1.0.0
21 +* Updated bundle 'com.emagiz.components.http' from 7.0.1 to 7.1.0
22 +* Updated bundle 'com.emagiz.components.staxon' from 1.0.0 to 1.1.0