The driver has been enhanced to allow you to define custom authentication requests, including the new CustomAuthParams connection property. If your service does not support one of the standard authentication methods supported by the driver, you can modify the input REST file to define a custom authentication flow. See Custom authentication for details.
The driver has been enhanced to allow you to customize how HTTP response status codes are processed by the driver. By configuring the input REST file, you can define error responses for codes that are returned by the service, including driver actions and error messages. See HTTP response code processing for details.
The driver has been enhanced to support OAuth 2.0 authentication. See OAuth 2.0 authentication for details.
The driver has been enhanced to support requests for endpoints that use custom HTTP-headers. See Creating an input REST file for details.
The driver supports JDBC core functions. See JDBC support for details.
The driver supports standard JSON data types and additional data types through data type inference. See Data types and getTypeInfo() for details.
The driver supports using internal memory or a configurable REST file to define REST responses and relational mapping. See Configuring the relational map for details.
The driver heuristically maps data types, eliminating the need to define native data types in most scenarios. See Data types for more information about data type mapping.
The driver supports basic, HTTP-header based, URL-Parameter based and no authentication. See Authentication for details.
The driver supports the handling of large result sets with configurable paging and the FetchSize and WSFetchSize connection properties. See Configuring the relational map for more information on configuring paging.