fixed

Authorization requests were not sent through the defined proxy.

fixed

When authenticating through OAuth2 with some of the flows, the token was unexpectedly regenerated even if the previous one was still valid

added

HTTP REST Metadata - ability to retrieve the whole response and map into one target field through a new extra field which is available in Mapping on the response node

added

OAuth2 Security - ability to send additional custom HTTP Headers during token generation through a new attribute in Metadata

added

Template - Integration Rdbms to HTTP - support using transparent stages

fixed

HTTP REST Metadata - when mapping a response JSON Property field to a stage, an error was thrown at execution during the load of data into the stage because the generated datatype was unexpectedly empty

fixed

HTTP REST Metadata - When mapping a response form value to a stage, an error was thrown at execution during the load of data into the stage because the generated datatype was unexpectedly empty

fixed

HTTP REST Metadata - The list on "type" attribute was empty on XML elements and XML attributes

fixed

OAuth2 Security - The "java.io.IOException: Pipe closed" exception could occur when executing a Mapping using the OAuth2 security

added

EMF compare utility - Component has been updated to support EMF Compare comparison utility

added

HTTP REST wizard - Ability to use string substitution variables inside the HTTP Rest wizard on the Reverse URL (such as %{env:variable_name}%)

added

HTTP REST Metadata - support defining proxy settings, which will be taken into account inside reverse wizards and operation executions

added

NTLM Authentication - adding a dedicated wizard on NTML security node, and support NTLM security node in HTTP Security Metadata

added

Proxy Metadata - Availabilty of a new Metadata to define Proxy settings

added

Addition of the "Nil_Behaviour" parameter to INTEGRATION Rdbms To Http template

added

Ability to use HTTP Rest Metadata in Mappings without input parameters

added

HTTP REST and HTTP Security OAuth2 Metadata - Two new metadata attributes have been added in HTTP REST technology and in HTTP Security Metadata, which allow to indicate if certificate and hostname verifications should be performed.

added

OAuth2 - Ability to externalize whole properties through a new "Json Properties" attribute containing a JSON representation of all the OAuth2 attributes and which is automatically generated

fixed

HTTP REST - Invocation was not performed because some output fields are sometimes automatically mapped with mapping when some names match with the source

fixed

Reverse REST Wizard - Invocation was failing when using an OAuth2 security node in which the Http Method is not set

fixed

Salesforce metadata - Fixing failed execution of a mapping that uses Salesforce Metadata with the OAuth2 Http security node

fixed

Template - INTEGRATION RDBMS to HTTP - Added new parameter "Write XML Key values" to write the value even if no data type defined on the key node

added

Ability to define and read response cookies

added

Support Multipart contents in Request Body

added

Support defining namespaces on the root node and to use them on XML contents

added

Web Services invocation - addition of new attributes in Metadata and Templates to declare a Connection Timeout and a Read Timeout

added

Web Service authentication with OAuth2 - a new parameter named "Send Client Credentials" has been added to define how client id and client secret should be sent, with the support of a new mode to send them in Basic Auth header

fixed

Default value proposed for the "Content-Type Header" attribute when using BINARY or XML Media Type was wrong

fixed

HTTP REST Metadata - the "new" context menu on a "Content" should propose an XML "element" node instead of an XML "root" node

fixed

HTTP Security - in Metadata, the different security nodes should be ordered by type

fixed

Responses items containing empty values, such as headers with empty values, were ignored

fixed

When having an XML Request content, root node name and attribute names defined in Metadata are ignored, the name sent is unexpectedly generated as "e" at execution instead of the real name

fixed

HTTP REST Component includes too much libraries dependencies, which makes its plugin size larger than expected

added

HTTP REST Component - new dedicated wizard to define security and reverse definition

added

HTTP REST Component - Allows to indicate if a parameter supports being sent with an empty value. (Note that an empty value is different than a null / not specified value, which is considered as if the parameter should not be sent at all)

added

HTTP REST Component - ability to reverse Open API 3 definitions