[JBoss JIRA] (TEIID-3177) Enforce SSL connections over ODBC when Encryption Mode is enabled
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3177?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3177:
---------------------------------------
Did you remove the ssl configuration from the transport? For ODBC it has ssl as disabled by default. With that config removed, then the ssl configuration defaults to login mode, which requires a secure login - effectively GSS for odbc.
> Enforce SSL connections over ODBC when Encryption Mode is enabled
> -----------------------------------------------------------------
>
> Key: TEIID-3177
> URL: https://issues.jboss.org/browse/TEIID-3177
> Project: Teiid
> Issue Type: Feature Request
> Components: ODBC
> Affects Versions: 8.8
> Reporter: Cristiano Nicolai
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.9, 8.7.5.6_2
>
>
> When connecting via ODBC transport, even if the encryption mode is set to enabled is still possible to establish non ssl connections. This allows clients to connect via insecure method. We would like that the Teiid transport could reject connections if they are not properly set up using SSL transport.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIID-3177) Enforce SSL connections over ODBC when Encryption Mode is enabled
by Juraj Duráni (JIRA)
[ https://issues.jboss.org/browse/TEIID-3177?page=com.atlassian.jira.plugin... ]
Juraj Duráni commented on TEIID-3177:
-------------------------------------
[~shawkins] ODBC transport now requires GSS authentication (according to message of SQLException) even if ssl is not enabled. Is this required behavior? (this concerns patch JDV 6.2.4 - Teiid 8.7.5.6_2)
Transport:
{code:xml}
<transport name="odbc" socket-binding="teiid-odbc" protocol="pg">
<authentication security-domain="teiid-security"/>
</transport>
{code}
ODBC DS:
{code:plain}
[odbc]
...
UserName = user
...
Password = user
SslMode = disable
{code}
Result:
{code:plain}
isql odbc -v
[08P01][unixODBC]ERROR: TEIID40125 A secure authentication is required, such as a GSS authentication.
[ISQL]ERROR: Could not SQLConnect
{code}
> Enforce SSL connections over ODBC when Encryption Mode is enabled
> -----------------------------------------------------------------
>
> Key: TEIID-3177
> URL: https://issues.jboss.org/browse/TEIID-3177
> Project: Teiid
> Issue Type: Feature Request
> Components: ODBC
> Affects Versions: 8.8
> Reporter: Cristiano Nicolai
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.9, 8.7.5.6_2
>
>
> When connecting via ODBC transport, even if the encryption mode is set to enabled is still possible to establish non ssl connections. This allows clients to connect via insecure method. We would like that the Teiid transport could reject connections if they are not properly set up using SSL transport.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIID-3878) java.lang.Integer cannot be cast to java.math.BigDecimal
by Mark Tawk (JIRA)
[ https://issues.jboss.org/browse/TEIID-3878?page=com.atlassian.jira.plugin... ]
Mark Tawk commented on TEIID-3878:
----------------------------------
I will try it as soon as possible on the latest version and get back to you.
> java.lang.Integer cannot be cast to java.math.BigDecimal
> --------------------------------------------------------
>
> Key: TEIID-3878
> URL: https://issues.jboss.org/browse/TEIID-3878
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.11.3
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 9.0
>
> Attachments: TEIID-3878.sql
>
>
> I'm using Teiid 8.11.3 with oracle translator.
> I have an aggregated query using teiid materialized views with the following simplified criteria:
> (CASE WHEN ( "table1"."field1" = 1 ) THEN "table2"."yearfield" ELSE null END IN (2014) )
> The above criteria is reproducing a ClassCastException Integer cannot be cast to BigDecimal
> if I change the criteria to the following, it passes without a problem:
> ("table2"."yearfield" IN (2014) )
> Here is the error stack:
> java.lang.ClassCastException: java.lang.Integer cannot be cast to java.math.BigDecimal
> at java.math.BigDecimal.compareTo(BigDecimal.java:219)
> at org.teiid.query.sql.symbol.Constant$2.compare(Constant.java:99)
> at org.teiid.query.eval.Evaluator.compare(Evaluator.java:581)
> at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:322)
> at org.teiid.query.eval.Evaluator.internalEvaluateTVL(Evaluator.java:236)
> at org.teiid.query.eval.Evaluator.evaluateTVL(Evaluator.java:225)
> at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:219)
> at org.teiid.query.processor.relational.JoinNode.matchesCriteria(JoinNode.java:353)
> at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy.process(EnhancedSortMergeJoinStrategy.java:460)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:227)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278)
> at org.teiid.query.processor.BatchCollector$BatchProducerTupleSource.nextTuple(BatchCollector.java:94)
> at org.teiid.query.processor.relational.GroupingNode.groupSortPhase(GroupingNode.java:490)
> at org.teiid.query.processor.relational.GroupingNode.nextBatchDirect(GroupingNode.java:366)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:148)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278)
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:457)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:339)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:267)
> at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:306)
> at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:238)
> at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:175)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:260)
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:173)
> at com.sun.proxy.$Proxy31.executeRequest(Unknown Source)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:667)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:533)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:1068)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:320)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIID-2476) Exclude hidden tables/columns from metadata
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2476?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2476.
-----------------------------------
Resolution: Done
Updated the code/tests for properties and keys. Added documentation about the table changes for performance and a release note / doc update for metadata visibility in general.
> Exclude hidden tables/columns from metadata
> -------------------------------------------
>
> Key: TEIID-2476
> URL: https://issues.jboss.org/browse/TEIID-2476
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Driver, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.0
>
>
> We should offer or possibly default to filtering tables/columns that can not accessed out of the user metadata. This should be done on the server side - however given the reuse we have of the system tables for example for materialized pg catalog queries - it is easier to add filters to the DatabaseMetadata (and ideally pg) metadata queries.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIID-3662) IN predicate against a materialized/temp table index without an order by returns wrong results
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3662?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3662:
------------------------------------------------
Debi Rieden <drieden(a)redhat.com> changed the Status of [bug 1257964|https://bugzilla.redhat.com/show_bug.cgi?id=1257964] from VERIFIED to CLOSED
> IN predicate against a materialized/temp table index without an order by returns wrong results
> ----------------------------------------------------------------------------------------------
>
> Key: TEIID-3662
> URL: https://issues.jboss.org/browse/TEIID-3662
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.7.1.6_2, 8.12, 8.11.3, 8.7.5
>
>
> Seeing strange behavior when doing a simple select from {{SPATIAL_REF_SYS}}.
> This works as expected:
> {code}
> select srid, proj4text from spatial_ref_sys where srid in (3875,4326);
> srid | proj4text
> ------+----------------------------------------------------------------------------------------------------------------
> 3875 | +proj=tmerc +lat_0=0 +lon_0=21 +k=1 +x_0=21500000 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs
> 4326 | +proj=longlat +datum=WGS84 +no_defs
> (2 rows)
> {code}
> Swapping the values in the IN causes only one row to be returned.
> {code}
> select srid, proj4text from spatial_ref_sys where srid in (4326,3875);
> srid | proj4text
> ------+-------------------------------------
> 4326 | +proj=longlat +datum=WGS84 +no_defs
> (1 row)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIID-4107) HSQL Syntax error when Teiid sends it a join query with no parenthesis
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4107?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4107:
----------------------------------
Issue Type: Bug (was: Feature Request)
Fix Version/s: 8.13.4
9.0.0
8.12.5
Affects Version/s: 7.0
Just a minor correction H2 was effectively a ground up restart by the HSQL creator, so they do share a lot in terms of initial design, sql support, etc., but no code - and the engines have continued to evolve independently.
> HSQL Syntax error when Teiid sends it a join query with no parenthesis
> ----------------------------------------------------------------------
>
> Key: TEIID-4107
> URL: https://issues.jboss.org/browse/TEIID-4107
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 7.0
> Reporter: Gabriel Steinberg
> Assignee: Steven Hawkins
> Fix For: 8.12.5, 8.13.4, 9.0.0
>
>
> The query
> SELECT R_NAME FROM region LEFT OUTER JOIN (customer INNER JOIN nation ON C_NATIONKEY = N_NATIONKEY) ON R_REGIONKEY = N_REGIONKEY
> When run against an HSQL DB causes a syntax error because the query passed to HSQL contains no parenthesis, and HSQL cannot handle it, as described in https://developer.jboss.org/message/953580?et=watches.email.thread#953580.
> As Steve points out there, this was solved for H2 in https://issues.jboss.org/browse/TEIID-3549. H2 and HSQL come from the same project, they split at some point in time, and I suspect they still share a lot of code.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIID-4077) Mysql5 translator - unknow column in having clause
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4077?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4077:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1318118|https://bugzilla.redhat.com/show_bug.cgi?id=1318118] from NEW to MODIFIED
> Mysql5 translator - unknow column in having clause
> --------------------------------------------------
>
> Key: TEIID-4077
> URL: https://issues.jboss.org/browse/TEIID-4077
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.5
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5
>
>
> Query:
> {code:sql}
> SELECT A.INTKEY, A.BYTENUM FROM BQT1.SMALLA AS A GROUP BY A.INTKEY, A.BYTENUM HAVING A.BYTENUM = (SELECT B.bytenum FROM BQT1.SMALLA AS B WHERE (B.INTNUM = 10))
> {code}
> Source specific query:
> {code:sql}
> SELECT g_0.INTKEY, cast(g_0.BYTENUM AS signed) FROM smalla AS g_0 GROUP BY g_0.INTKEY, cast(g_0.BYTENUM AS signed) HAVING cast(g_0.BYTENUM AS signed) = (SELECT cast(g_1.BYTENUM AS signed) FROM smalla AS g_1 WHERE g_1.INTNUM = 10)
> {code}
> Exception:
> {code:plain}
> 07:33:07,377 WARN [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue36) Connector worker process failed for atomic-request=Z7YmVoh18LjC.13.2.6: org.teiid.translator.jdbc.JDBCExecutionException: 1054 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.INTKEY, cast(g_0.BYTENUM AS signed) FROM smalla AS g_0 GROUP BY g_0.INTKEY, cast(g_0.BYTENUM AS signed) HAVING cast(g_0.BYTENUM AS signed) = (SELECT cast(g_1.BYTENUM AS signed) FROM smalla AS g_1 WHERE g_1.INTNUM = 10)]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.5.redhat-2.jar:8.12.5.redhat-2]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:359)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0-internal]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0-internal]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0-internal]
> at java.lang.reflect.Method.invoke(Method.java:483) [rt.jar:1.8.0-internal]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy22.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0-internal]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0-internal]
> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'g_0.BYTENUM' in 'having clause'
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.8.0-internal]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) [rt.jar:1.8.0-internal]
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.8.0-internal]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:408) [rt.jar:1.8.0-internal]
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
> at com.mysql.jdbc.Util.getInstance(Util.java:386)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1053)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4096)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4028)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2490)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2734)
> at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155)
> at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2322)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123) [translator-jdbc-8.12.5.redhat-2.jar:8.12.5.redhat-2]
> ... 18 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIID-4094) Move the packaging of teiid-jdbc.jar into is own project
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4094?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4094:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1318684|https://bugzilla.redhat.com/show_bug.cgi?id=1318684] from ASSIGNED to MODIFIED
> Move the packaging of teiid-jdbc.jar into is own project
> --------------------------------------------------------
>
> Key: TEIID-4094
> URL: https://issues.jboss.org/browse/TEIID-4094
> Project: Teiid
> Issue Type: Enhancement
> Components: Build/Kits
> Affects Versions: 8.12.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 9.0, 8.12.5
>
>
> The issue with the way the teiid-jdbc.jar is packaged now, is that the teiid-web-console.zip gets included as a dependency.
> {code}
> [INFO] +- org.jboss.teiid:teiid:jar:jdbc:8.12.5.redhat-2:compile
> [INFO] | \- org.jboss.teiid.web-console:teiid-console-dist:zip:jboss-as7:2.5.6.Final-redhat-63-4:compile
> {code}
> And that becomes an issue when other external projects to Teiid include the jdbc driver as a dependency, in that they also end up requiring the web-console.zip.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months