HTTP REST Component Release Notes

DI-8273: The REST wizard mismatches the reversed nodes when using it multiple times without closing the metadata.

DI-9649: Fixed an issue with the WSDL wizard that prevented SSL authentication when certificate validation was disabled.

DI-9534: Fixed an issue where the Write Xml Key option did not work.

DI-7854: Fixed an issue which prevented HTTP REST or WSDL authentication with some SSL configurations such as Mutual SSL authentication.

DI-9308: Fixed an issue which showed an error when creating an OAuth2 entry for login.microsoftonline.com.

DI-8926: Update SnakeYAML third-party libraries.

DI-8273: The REST wizard mismatches reversed nodes when used multiple times without closing the REST metadata it is launched from.

DI-8530: Add tooltips for functional and technical error parameters.

DI-7845: HTTP REST Reverse wizard: The response structure and parameters are missing from the selective reverse step.

DI-7836: When trying to generate an OAuth2 token while the security metadata have some defined auth parameters or HTTP headers, the error Failed to generate OAuth 2 Authorization Header is displayed.

DI-7262: OAuth2 requests a new token even if a former token is still valid

DI-7089: An error is thrown if the Part Name field contains square brackets, that is, [ and ] characters.

DI-6697: The INTEGRATION Rdbms to Http template ignored the enableHostnameVerification and enableCertificateVerification options. They are now properly handled. As they are enabled by default, you might experience certificate verification errors if you are using APIs with self-signed certificates. In this situation, disable these parameters.

DI-2556: In the metadata, in the Standard finger tab, the Keystore and Truststore parameters have been added. These parameters can be used to define custom keystore and truststore during REST API calls.

DI-4732: The OUT_FILE_NAME parameter has been added to the INTEGRATION Rdbms to HTTP template.

DI-5334: The Reverse REST and HTTP Security wizards have been moved from the designer to the HTTP REST component.

DI-5345: When creating HTTP REST metadata, the text/csv can now be select in the Content-Type Header list.

DI-5758: When performing a selective reverse, a progress bar is displayed to inform the user that an operation is running.

DI-6720: The Keystore and Truststore parameters are supported in wizards.

DI-5389: The metadata reverse-engineering has been improved.

DI-4150: The URL field in reverse page does not resize correctly when the string is too long.

DI-4497: Wizards do not propose a scroll bar on small screens or when resizing them. This makes certain fields inaccessible.

DI-5031: When using the Reverse REST wizard inside WSDL Metadata, the NTLM security nodes are not visible.

DI-5072: When reversing an Open API 3 definition on a a file or a URL having special characters in the path, the Unable to read location error is thrown.

DI-5320: When creating an oauth1 security node through the dedicated wizard, the wizard ignores the default values of various lists.

DI-5736: The java.lang.NoClassDefFoundError: io/swagger/v3/core/util/Json error is thrown when reverse-engineering some Open API definitions.

DI-6314: SnakeYAML - Third-party library upgrade.

DI-6333: HttpClient - Third-party library upgrade.

DI-6461: When running multiple data flows with different OAuth2 tokens, the tokens are mismatched with each other, leading to authentication errors.

DI-6697: The INTEGRATION Rdbms to Http template ignores the enableHostnameVerification and enableCertificateVerification options.

DI-6701: Passwords containing special characters are not encoded correctly when generating OAuth2 tokens. This leads to failed authentication.

DI-6382: The Outgoing Server (SMPTP) and Incoming Account nodes in the email metadata now support Microsoft Outlook’s modern authentication system based on a token mechanism. See Getting Started with Email Server

DI-602: HTTP REST Component - ability to reverse Open API 3 definitions

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

DI-1974: 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)

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

DI-1739: Support Multipart contents in Request Body

DI-2669: Ability to define and read response cookies

DI-2674: Support defining namespaces on the root node and to use them on XML contents

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

DI-1828: 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

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

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

DI-3057: Responses items containing empty values, such as headers with empty values, were ignored

DI-2683: 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

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

DI-3387: 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.

DI-3429: Addition of the "Nil_Behaviour" parameter to INTEGRATION Rdbms To Http template

DI-3531: Ability to use HTTP Rest Metadata in Mappings without input parameters

DI-1252: 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

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

DI-2975: 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

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

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

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

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

DI-2822: Proxy Metadata - Availabilty of a new Metadata to define Proxy settings

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

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

DI-3339: 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

DI-3553: 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

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

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

DI-1750: 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

DI-2962: Template - Integration Rdbms to HTTP - support using transparent stages

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

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

DI-128: JSON Metadata: Reverse-engineering JSON schemas

DI-2477: New metadata wizards automatically select all the listed elements for selective reverse-engineering.

DI-2480: HTTP REST: Reverse-engineering XML structures from XML schemas

DI-2973: HTTP REST metadata wizard supports reverse-engineering the response Set-Cookies headers.

DI-3701: Allow Components to contribute to Designer monitored statistics

DI-4153: JSON writing - ability to choose how to write empty objects and arrays

DI-4335: HTTP REST: Configure retries, functional response codes and error messages capture to handle errors occurring on API calls.

DI-4508: Update Components and Designer to take into account dedicated license permissions

DI-4727: Rebranding: Templates and sample projects

DI-4800: HTTP Security and HTTP Proxy are now included as base components

DI-4962: Improved component dependencies and requirements management

DI-4382: HTTPS operations do not work when a proxy is defined

DI-5216: Authorization requests were not sent through the defined proxy

DI-5736 : Error "java.lang.NoClassDefFoundError: io/swagger/v3/core/util/Json" when trying to reverse-engineering some Open API definitions.