Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | Small update that fixes three specific issues. | ||
| 2 | |||
| 3 | ===== Minor Changes ===== | ||
| 4 | |||
| 5 | * Updated bundle 'com.emagiz.bundles.groovy-all' from 3.0.9.1 to 3.0.9.2 | ||
| 6 | * Removed bundle 'com.sun.mail.javax.mail' because it was not used anymore | ||
| 7 | * Updated bundle 'com.emagiz.components.security' from 7.1.1 to 7.2.0 | ||
| 8 | * Updated bundle 'com.emagiz.components.http' from 7.2.1 to 7.2.2 | ||
| 9 | * Updated bundle 'com.emagiz.util.codec' from 6.1.0 to 6.1.1 | ||
| 10 | |||
| 11 | ===== Bug Fixes ===== | ||
| 12 | |||
| 13 | * The OAuth 2.0 authorization interceptor in the Rest Template component contained client 'Authentication methods’ that were invalid and caused a flow not to start in build 59. Also the clockskew is now configurable so we can handle the requirements of more oauth2 authentication providers. | ||
| 14 | * The Amazon S3 authentication interceptor in the Rest Template component had a threading issue where the key would be invalid on heavy usage. The threading has been changed and is now behaving correctly. | ||
| 15 | * In several flow designer components you can add Groovy scripts. Since build 59 using FastStringUtils (JSON parsing) did not work. | ||
| 16 | * For Gen3 runtimes we upgraded to Spring Boot 2.6.6 to bring the latest security patches. | ||
| 17 | |||
| 18 | ==== Known issues ==== | ||
| 19 | * In case a flow doesn't start properly and that flow contains HTTP components, please try to create a new flow version from Create and use that version in your release. In some specific cases, a duplicate chain error message could appear that indicates this specific case. |