[JBoss JIRA] (TEIID-4081) SSL - server accepts any client certificate
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4081?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4081.
---------------------------------
> SSL - server accepts any client certificate
> -------------------------------------------
>
> Key: TEIID-4081
> URL: https://issues.jboss.org/browse/TEIID-4081
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.12.5
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Priority: Blocker
> Attachments: keystore_client_expired.jks, keystore_client_root_expired.jks, keystore_client_untrusted.jks, keystore_server.jks, truststore.jks, truststore_expired.jks
>
>
> In 2-way authentication mode client must provide to the server valid certificate. But Teiid accepts any certificate which client provides.
> * expired
> * untrusted
> * signed by certificate of root CA which already expired
> Teiid should reject such client's certificate and fail to establish connection.
> On the client side, paths are set using teiid-specific properties:
> {code:java}
> System.setProperty("org.teiid.ssl.keyStore", clientKeystorePath);
> System.setProperty("org.teiid.ssl.keyStorePassword", "keystorepswd");
> System.setProperty("org.teiid.ssl.keyAlias", "client");
> System.setProperty("org.teiid.ssl.keyPassword", "keystorepswd");
> System.setProperty("org.teiid.ssl.trustStore", clientTruststorePath);
> System.setProperty("org.teiid.ssl.trustStorePassword", "truststorepswd");
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIID-4022) Materialization issue dynamic SQL command can't be executed due ambiguous group name
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4022?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4022.
---------------------------------
> Materialization issue dynamic SQL command can't be executed due ambiguous group name
> --------------------------------------------------------------------------------------
>
> Key: TEIID-4022
> URL: https://issues.jboss.org/browse/TEIID-4022
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.12.x
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 9.0, 8.12.5, 8.13.2
>
>
> The defined model for materialization:
> {code}
> <model name="PersonMatModel" type="VIRTUAL">
> <metadata type="DDL"><![CDATA[
> CREATE view PersonMatView
> (
> name string,
> id integer,
> email string
> ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'TRUE',
> MATERIALIZED_TABLE 'PersonMatCache.Person',
> "teiid_rel:MATVIEW_TTL" 60000,
> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute PersonMatCache.native(''truncate cache'');',
> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute PersonMatCache.native(''swap cache names'');',
> "teiid_rel:MATERIALIZED_STAGE_TABLE" 'PersonMatCache.Person',
> "teiid_rel:MATVIEW_SHARE_SCOPE" 'NONE',
> "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true',
> "teiid_rel:MATVIEW_STATUS_TABLE" 'Accounts.status',
> "teiid_rel:MATVIEW_ONERROR_ACTION" 'THROW_EXCEPTION')
> AS SELECT name, id, email from PersonInfoModel.Person;
> ]]>
> </metadata>
> </model>
> {code}
> causes the following exception:
> {code}
> org.teiid.api.exception.query.QueryProcessingException: TEIID30168 Couldn't
> execute the dynamic SQL command "EXECUTE IMMEDIATE ('SELECT count(*) as
> rowCount FROM ' || matViewTable) AS rowCount integer INTO #load_count" with
> the SQL statement "('SELECT count(*) as rowCount FROM ' || matViewTable)" due
> to: Group specified is ambiguous, resubmit the query by fully qualifying the group
> name: Person
> {code}
> And executing the following internal call that Teiid uses does produce the non-qualifed name
> {ccode}
> SELECT TargetName from SYSADMIN.MatViews WHERE VDBName = 'PeopleMat' AND SchemaName = 'PersonMatModel' AND Name = 'PersonMatView'
> {code}
> returns: Person
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIID-4083) MongoDB: Can't connect to mongodb using username/password auth
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4083?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4083.
---------------------------------
> MongoDB: Can't connect to mongodb using username/password auth
> --------------------------------------------------------------
>
> Key: TEIID-4083
> URL: https://issues.jboss.org/browse/TEIID-4083
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.5
> Environment: MongoDB 3.x
> DV 6.3 ER1
> Reporter: Filip Elias
> Assignee: Ramesh Reddy
>
> I can't connect to MongoDB through mongodb translator. An authentication always fails.
> Server exception:
> {code}
> 14:14:15,304 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Worker3_QueryProcessorQueue4) mongodb-ds: getConnection(null, null) [0/20]
> 14:14:15,305 INFO [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue4) SELECT smalla.INTNUM AS c_0, smalla.BIGDECIMALVALUE AS c_1, smalla.BIGINTEGERVALUE AS c_2, smalla.BOOLEANVALUE AS c_3, smalla.BYTENUM AS c_4, smalla.CHARVALUE AS c_5, smalla.DATEVALUE AS c_6, smalla.DOUBLENUM AS c_7, smalla.FLOATNUM AS c_8, smalla.INTKEY AS c_9, smalla.LONGNUM AS c_10, smalla.OBJECTVALUE AS c_11, smalla.SHORTVALUE AS c_12, smalla.STRINGKEY AS c_13, smalla.STRINGNUM AS c_14, smalla.TIMESTAMPVALUE AS c_15, smalla.TIMEVALUE AS c_16 FROM smalla LIMIT 100
> 14:14:16,229 WARN [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue4) Connector worker process failed for atomic-request=ysa307n2BRiE.1.0.1: org.teiid.translator.TranslatorException: { "serverUsed" : "dvqe03.mw.lab.eng.bos.redhat.com:27017" , "ok" : 0.0 , "errmsg" : "auth failed" , "code" : 18}
> at org.teiid.translator.mongodb.MongoDBQueryExecution.execute(MongoDBQueryExecution.java:104) [translator-mongodb-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_45]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_45]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_45]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_45]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy125.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_45]
> 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_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45]
> Caused by: com.mongodb.CommandFailureException: { "serverUsed" : "dvqe03.mw.lab.eng.bos.redhat.com:27017" , "ok" : 0.0 , "errmsg" : "auth failed" , "code" : 18}
> at com.mongodb.CommandResult.getException(CommandResult.java:76) [mongo-java-driver-2.13.1.jar:]
> at com.mongodb.CommandResult.throwOnError(CommandResult.java:140) [mongo-java-driver-2.13.1.jar:]
> at com.mongodb.DBPort$NativeAuthenticator.authenticate(DBPort.java:986) [mongo-java-driver-2.13.1.jar:]
> at com.mongodb.DBPort.authenticate(DBPort.java:432) [mongo-java-driver-2.13.1.jar:]
> at com.mongodb.DBPort.checkAuth(DBPort.java:443) [mongo-java-driver-2.13.1.jar:]
> at com.mongodb.DBTCPConnector.innerCall(DBTCPConnector.java:289) [mongo-java-driver-2.13.1.jar:]
> at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:269) [mongo-java-driver-2.13.1.jar:]
> at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:84) [mongo-java-driver-2.13.1.jar:]
> at com.mongodb.DB.command(DB.java:320) [mongo-java-driver-2.13.1.jar:]
> at com.mongodb.DB.command(DB.java:299) [mongo-java-driver-2.13.1.jar:]
> at com.mongodb.DBCollectionImpl.aggregate(DBCollectionImpl.java:99) [mongo-java-driver-2.13.1.jar:]
> at com.mongodb.DBCollection.aggregate(DBCollection.java:1649) [mongo-java-driver-2.13.1.jar:]
> at org.teiid.translator.mongodb.MongoDBQueryExecution.execute(MongoDBQueryExecution.java:102) [translator-mongodb-8.12.5.redhat-2.jar:8.12.5.redhat-2]
> ... 18 more
> 14:14:16,238 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Worker2_QueryProcessorQueue5) mongodb-ds: returnConnection(12a738da, false) [1/20]
> 14:14:16,240 WARN [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue5) TEIID30020
> {code}
> MongoDB log:
> {code}
> 16.141-0400 I ACCESS [conn704] authenticate db: bqt { authenticate: 1, user: "dv", nonce: "xxx", key: "xxx" }
> 2016-03-16T09:14:16.141-0400 I ACCESS [conn704] Failed to authenticate dv@bqt with mechanism MONGODB-CR: AuthenticationFailed: MONGODB-CR credentials missing in the user document
> {code}
> You can find resource-adapter config in the corresponding bugzilla.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIID-4049) OData 4 query hangs in test run
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4049?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4049.
---------------------------------
> OData 4 query hangs in test run
> -------------------------------
>
> Key: TEIID-4049
> URL: https://issues.jboss.org/browse/TEIID-4049
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> During the run of:
> org.teiid.olingo.TestODataIntegration.testExpandSimple(TestODataIntegration.java:988)
> The server seems to be in an indefinite wait state:
> "qtp1207140081-380" #380 prio=5 os_prio=0 tid=0x00007f7c94bbb800 nid=0x3642 in Object.wait() [0x00007f7c6a6cc000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:287)
> - locked <0x0000000770e1c130> (a org.teiid.dqp.internal.process.RequestWorkItem)
> at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:313)
> at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:245)
> at sun.reflect.GeneratedMethodAccessor103.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:190)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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:188)
> at com.sun.proxy.$Proxy15.executeRequest(Unknown Source)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:673)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:539)
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:260)
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:73)
> at org.teiid.olingo.service.LocalClient.executeSQL(LocalClient.java:228)
> at org.teiid.olingo.service.TeiidServiceHandler.executeQuery(TeiidServiceHandler.java:347)
> at org.teiid.olingo.service.TeiidServiceHandler.read(TeiidServiceHandler.java:167)
> at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.execute(DataRequest.java:302)
> at org.apache.olingo.server.core.requests.DataRequest.execute(DataRequest.java:245)
> at org.apache.olingo.server.core.ServiceDispatcher.execute(ServiceDispatcher.java:117)
> at org.apache.olingo.server.core.OData4HttpHandler.process(OData4HttpHandler.java:65)
> at org.teiid.olingo.web.ODataServlet.service(ODataServlet.java:50)
> Just trying to run the test or the whole test class in isolation through many iterations has not reproduced this, so I'm logging this for now in hopes that if others see this we may get more details as to when it occurs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIID-4026) Web Admin Console: Invalid attribute in SSL configuration
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4026?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4026.
---------------------------------
> Web Admin Console: Invalid attribute in SSL configuration
> ---------------------------------------------------------
>
> Key: TEIID-4026
> URL: https://issues.jboss.org/browse/TEIID-4026
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 8.12.5
> Environment: ER1
> Reporter: Filip Elias
> Assignee: Steven Hawkins
>
> It seems ssl-enable is invalid attribute (ssl can be enabled through attribute 'mode'). I assume it can be removed from menu. Configuration fails when SSL Enabled is checked.
> Error:
> {code}
> Unknown error
> Unexpected HTTP response: 500
> Request
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [{
> "address" => [
> ("subsystem" => "teiid"),
> ("transport" => "embedded")
> ],
> "operation" => "write-attribute",
> "name" => "ssl-enable",
> "value" => true
> }]
> }
> Response
> Internal Server Error
> {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "failure-description" => "JBAS014792: Unknown attribute ssl-enable",
> "rolled-back" => true
> }},
> "failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014792: Unknown attribute ssl-enable"}},
> "rolled-back" => true,
> "response-headers" => {"process-state" => "reload-required"}
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIID-3005) Support Kerberos pass-thru to the data source
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3005?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3005.
---------------------------------
> Support Kerberos pass-thru to the data source
> ---------------------------------------------
>
> Key: TEIID-3005
> URL: https://issues.jboss.org/browse/TEIID-3005
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Critical
>
> Need to add support for Kerberos authentication pass-thru all the way to the data source, for data sources that support Kerberos, of course. Besides relational data sources, could it also support Cloudera Hadoop Distribution.
> This maybe a duplicate of other pass-thru related jira's, but wasn't sure, so I logged this to at least get confirmation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIID-3996) SAP HANA materialization: MATVIEW_ONERROR_ACTION set to WAIT problem
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3996?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3996.
---------------------------------
> SAP HANA materialization: MATVIEW_ONERROR_ACTION set to WAIT problem
> --------------------------------------------------------------------
>
> Key: TEIID-3996
> URL: https://issues.jboss.org/browse/TEIID-3996
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.x
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> When using materialization wit SAP HANA datasource, a problem emerges when "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT' is defined for the materialized view.
> The query which initiates matview's loading doesn't wait for its completion, thus returns stale data (empty resultset in case of the initial invocation).
> Materialized view definition:
> {code:sql}
> CREATE VIEW external_long_ttl (
> customer_id integer NOT NULL,
> total_amount integer
> ) OPTIONS (
> MATERIALIZED 'TRUE',
> UPDATABLE 'FALSE',
> MATERIALIZED_TABLE 'Source.JSTASTNY.dv_matviews_mat_view',
> "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true',
> "teiid_rel:MATVIEW_STATUS_TABLE" 'Source.JSTASTNY.dv_matviews_statustable',
> "teiid_rel:ON_VDB_START_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_create) SELECT id, vdb_create+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:ON_VDB_DROP_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_drop) SELECT id, vdb_drop+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_LOAD_SCRIPT" 'INSERT INTO dv_matviews_mat_view_stage(customer_id,total_amount) SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;',
> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'exec Source.native(''truncate table dv_matviews_mat_view_stage'');MERGE INTO dv_matviews_check_table(id,before_load) SELECT id, before_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''RENAME TABLE dv_matviews_mat_view_stage TO dv_matviews_mat_view_temp'');exec Source.native(''RENAME TABLE dv_matviews_mat_view TO dv_matviews_mat_view_stage'');exec Source.native(''RENAME TABLE dv_matviews_mat_view_temp TO dv_matviews_mat_view'');MERGE INTO dv_matviews_check_table(id,after_load) SELECT id, after_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT',
> "teiid_rel:MATVIEW_TTL" 20000
> ) AS SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;
> {code}
> Query performed:
> {code:sql}
> SELECT * FROM external_long_ttl;
> {code}
> Reproducer:
> {code:java}
> Statement statement = connection.createStatement();
> // invoke initial load, won't return loaded data even though it should
> ResultSet rs1 = statement.executeQuery("SELECT * FROM external_long_ttl;");
> Assert.assertFalse(rs1.next());
> // wait explicitly for the loading to finish
> Thread.sleep(7000);
> // repeat the query, to get the data after load finished
> ResultSet rs2 = statement.executeQuery("SELECT * FROM external_long_ttl;");
> Assert.assertTrue(rs2.next());
> .
> .
> .
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years