Extension of SQL Syntax for Certificate Verification in EXA to EXA Import and Export
Details
| Detail name | Value |
|---|---|
| Changelog Number | 21747 |
| Type | Improvement |
| Status | Resolved |
| Fix Versions | Exasol 8.33.0 |
| Resolution Date | 2025-02-27 |
Background
In database version 8.32.0 IMPORT and EXPORT functionality was extended to allow specifying how to verify certificates when working with file connections (CSV, FBV, LOCAL files).
In version 8.33.0 such functionality is also added for IMPORT/EXPORT FROM/TO EXA commands.
Improvement
Extension of SQL Syntax for Certificate Verification in EXA to EXA Import and Export
In the ongoing effort to enhance and streamline database functionalities, the SQL syntax has been extended to offer increased flexibility with certificate verification during EXA to EXA data migrations. This update fine-tunes the existing interface to allow users to enable or disable certificate validation seamlessly.
Updated SQL Certificate Verification Syntax
This update introduces the following options to configure certificate verification directly in IMPORT and EXPORT statements:
- VERIFY CERTIFICATE: Activates certificate verification, mapping to the ODBC connection string parameter SSLCertificate=SSL_VERIFY_SERVER.
- IGNORE CERTIFICATE: Deactivates certificate verification, mapping to the ODBC connection string parameter SSLCertificate=SSL_VERIFY_NONE.
- PUBLIC KEY '******':* Specifies the fingerprint for certificate verification, mapping to the ODBC connection string parameter Fingerprint=*******. This option takes precedence over other certificate verification settings.
Example SQL Syntax
-- Activate certificate verification and provide a public key IMPORT INTO Test.DB FROM EXA AT 'localhost:8511' VERIFY CERTIFICATE PUBLIC KEY 'xxxxxxxxxx' Table Test.T; -- Deactivate certificate verification IMPORT INTO Test.DB FROM EXA AT 'localhost:8511' IGNORE CERTIFICATE Table Test.T; -- Provide only a public key for certificate validation IMPORT INTO Test.DB FROM EXA AT 'localhost:8511' PUBLIC KEY 'xxxxxxxxxx' Table Test.T;
Default Behavior
By default, TLS certificate verification is activated during EXA to EXA transactions. However, users can override this behavior using the newly introduced SQL syntax or through connection string parameters as needed.
For further information regarding the SQL Syntax, please refer to the changelog entry CHANGELOG: TLS Certificate Verification for Loader File Connections (CSV, FBV, LOCAL files).