search

exasol / exasol-virtual-schema

Virtual Schema from Exasol to Exasol
MIT License
1 stars 2 forks source link

Password is exposed in EXPLAIN VIRTUAL for EXA connections #24

Closed snehlsen closed 3 years ago

snehlsen commented 5 years ago

If a connection is used in a Virtual Schema that stores username and password, this information should not be exposed in the resulting pushdown SQL. This works fine for JDBC connections, but not for the special EXA connection:

CREATE CONNECTION sys_connection TO 'jdbc:exa:localhost:42627' USER 'SYS' IDENTIFIED BY 'exasol';
CREATE VIRTUAL SCHEMA vs USING adapter.jdbc_adapter
WITH connection_name = 'SYS_CONNECTION' 
sql_dialect='EXASOL' schema_name = 'LS' 
import_from_exa='TRUE' exa_connection_string='localhost:42627';

Execution of explain virtual select x from vs.t; returns the pushdown: IMPORT FROM EXA AT 'localhost:42627' USER 'SYS' IDENTIFIED BY 'exasol' STATEMENT 'SELECT * FROM "LS"."T"'

The question is why do we need a special exa_connection_string? If this is redundant we can just use the information from the provided connection. However this would be changed behavior.

AnastasiiaSergienko commented 5 years ago

Closed with exasol/virtual-schemas#95