11 REDSHIFT
============================================================================== Simba Amazon Redshift ODBC Driver Release Notes ==============================================================================
The release notes provide details of enhancements, features, and known issues in Simba Amazon Redshift ODBC Driver 1.4.3, as well as the version history.
1.4.3 ========================================================================
Released 2018-09-14
Enhancements & New Features
[PGODBC-1007] Proxy support for IAM authentication processes
You can now configure the driver to pass IAM authentication processes through a proxy server. For more information, see the Installation and Configuration Guide.
[PGODBC-1015] Upgraded OpenSSL library
The driver now uses OpenSSL 1.1.0i.
[PGODBC-1004] Standardized log file names
When logging is enabled, the driver now produces the following log files:- A simbaredshiftodbcdriver.log file that logs driver activity that is not specific to a connection.
- A simbaredshiftodbcdriver_connection_[Number].log for each connection made to the database, where [Number] is a number that identifies each log file. This file logs driver activity that is specific to the connection.
[PGODBC-996] More informative SSL error messages
The driver now provides more detailed error messages for TLS/SSL errors.
Resolved Issues The following issue has been resolved in Simba Amazon Redshift ODBC Driver 1.4.3.
- [PGODBC-1005] When the driver is configured to connect to Redshift through a proxy server, if the Server property is set to an IP address instead of a host name, the driver does not recognize the IP address and fails to connect to Redshift.
Known Issues The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.
Timestamps do not accept negative values.
The driver does not support the use of negative values in timestamps.
Version History ==============================================================
1.4.2 ————————————————————————
Released 2018-06-28
Enhancements & New Features
[PGODBC-932] Extended support for credentials provider services on Windows
The Windows driver now supports credentials services aside from AD FS, PingFederate, and Okta. The service must be available as a SAML-based credential provider plugin. For more information, see the Installation and Configuration Guide.
[PGODBC-339] Authentication support added for proxy connections
You can now provide credentials to authenticate proxy connections. To do this, set the Proxy Username (or ProxyUid) option to your user name for accessing the proxy server, and set the Proxy Password (or ProxyPwd) option to the corresponding password. For more information, see the Installation and Configuration Guide.
[PGODBC-981] Improved parsing for endpoints that use a domain other than “.com”
The driver can now automatically identify the cluster ID when connecting to an endpoint that uses a domain other than “.com”, such as endpoints that use “.cn” or other regional domains.
[PGODBC-988] Updated third-party dependencies
The driver now uses the following versions of these third-party libraries:- OpenSSL 1.1.0h (previously OpenSSL 1.1.0g)
- libcURL 7.60.0 (previously 7.52.1)
- zlib 1.2.11 (previously 1.2.8)
As a result, several security features in the driver have been improved.
Resolved Issues The following issues were resolved in Simba Amazon Redshift ODBC Driver 1.4.2.
[PGODBC-985] In some cases, when calling APIs, the driver does not escape filter parameters correctly.
[PGODBC-982] When configuring the driver using the ODBC Administrator on Windows, if you configure proxy connection settings and then click the “Test” button, the ODBC Administrator terminates unexpectedly.
[PGODBC-983] If the server name contains hexidecimal characters only, the driver terminates unexpectedly when attempting to connect to the server.
[PGODBC-239] When configuring the driver using the ODBC Administrator on Windows, if you enter a DSN name that contains special characters and then click the “Test” button, the ODBC Administrator terminates unexpectedly.
This issue has been resolved. The driver now returns an error message instead of causing the ODBC Administrator to terminate unexpectedly.
[PGODBC-886] When retrieving a DOUBLE value that is larger than the maximum value supported by the DOUBLE data type, the driver returns INFINITY (or Null in some applications) instead of the maximum DOUBLE value.
[PGODBC-995] In some cases, when using PingFederate authentication, the driver fails to connect during the first attempt but succeeds during subsequent connection attempts.
1.4.1 ————————————————————————
Released 2018-01-31
Enhancements & New Features
Amazon EC2 instance profile support
You can now configure the driver to authenticate your connection using an Amazon EC2 instance profile. To do this, enable the new Use Instance Profile option (the InstanceProfile property) when configuring profile authentication. For more information, see the Installation and Configuration Guide.
Partner SPID support
When configuring authentication using the PingFederate service, you can now specify a partner SPID (service provider ID) value. To do this, set the new Partner SPID option (the partner_spid property) to the ID value. For more information, see the Installation and Configuration Guide.
Okta application name support
When configuring authentication using the Okta service, you can now specify the Okta application name. To do this, set the new Okta App Name option (the App_Name property) to the name of the application. For more information, see the Installation and Configuration Guide.
Improved support for AD FS authentication
Driver support for AD FS server settings has been improved through internal updates.
Improved support for character sets in internal processes
The driver now supports non-ASCII character sets in connection attributes and error messages.
Resolved Issues The following issue was resolved in Simba Amazon Redshift ODBC Driver 1.4.1.
In some cases, when calling SQLBindParameter and then SQLPrepare, the driver truncates the data and returns an error.
This issue has been resolved. Before, the driver used a fixed VarChar column length of 255. If the data length was longer than 255 characters, the driver would truncate the data and return the following message:
“[Amazon][ODBC] (10170) String data right truncation on data from data source: String data is too big for the driver’s data buffer”
The driver now uses the column length specified in the Max VarChar option (the MaxVarChar property) instead of a fixed value, so you can specify a larger maximum VarChar column size and avoid this issue.
1.4.0 ————————————————————————
Enhancements & New Features
Internal driver improvements
The driver has been updated with minor internal improvements.
==============================================================================