[JBoss JIRA] (TEIID-4080) Prevent expired client/server certificates from being accepted
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4080?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4080:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1318154|https://bugzilla.redhat.com/show_bug.cgi?id=1318154] from NEW to MODIFIED
> Prevent expired client/server certificates from being accepted
> --------------------------------------------------------------
>
> Key: TEIID-4080
> URL: https://issues.jboss.org/browse/TEIID-4080
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 8.12.5
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5
>
> Attachments: keystore_client.jks, keystore_server_root_expired.jks, truststore.jks, truststore_expired.jks
>
>
> If SSL is enabled (1-way or 2-way) server provides to the client certificate which must be signed by valid certificate of trusted CA.
> If server provides certificate which is signed by certificate of root CA which already expired client accepts this certificate. Client should not accept such certificate.
> This affects 1-way and 2-way authentication modes.
> 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)
10 years
[JBoss JIRA] (TEIID-4080) Prevent expired client/server certificates from being accepted
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4080?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4080.
-----------------------------------
Fix Version/s: 9.0
8.12.5
Resolution: Done
Added the client property org.teiid.ssl.checkExpired and the transport property truststore-check-expired to look for valid certificate dates. Both default to false for backwards compatibility.
> Prevent expired client/server certificates from being accepted
> --------------------------------------------------------------
>
> Key: TEIID-4080
> URL: https://issues.jboss.org/browse/TEIID-4080
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 8.12.5
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5
>
> Attachments: keystore_client.jks, keystore_server_root_expired.jks, truststore.jks, truststore_expired.jks
>
>
> If SSL is enabled (1-way or 2-way) server provides to the client certificate which must be signed by valid certificate of trusted CA.
> If server provides certificate which is signed by certificate of root CA which already expired client accepts this certificate. Client should not accept such certificate.
> This affects 1-way and 2-way authentication modes.
> 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)
10 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 resolved TEIID-3005.
-----------------------------------
Resolution: Done
Marking as done based upon the comments.
> 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)
10 years
[JBoss JIRA] (TEIID-3015) ODATA: Duplicate NavigationProperty name
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3015?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3015:
---------------------------------------
There's no need to reopen this issue as both the odata4 and odata2 are correct.
> ODATA: Duplicate NavigationProperty name
> ----------------------------------------
>
> Key: TEIID-3015
> URL: https://issues.jboss.org/browse/TEIID-3015
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: Beta3
> Fix For: 8.8, 8.7.1
>
>
> Entity 1: TransferRule
> Entity 2: FinancialAccount
> TransferRule
> - sourceAccount : FinancialAccount
> - destination : FinancialAccount
> - other attributes
> the mapping to this for odata resolves to
> <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_destinationfinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" />
> <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_sourcefinancial_account_id_fk" FromRole="transferrule"
> ToRole="financialaccount" />
> The navigation property name is duplicated with in transfer rule entity.
> Hence some of the Odata client see it as ambiguous element
> Is there a way to customise the Name to
> Name="src_financialaccount" and
> Name="dest_financialaccount"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (TEIID-4097) No active transaction found while executing long running update statement
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4097?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4097:
---------------------------------------
Yes that looks like it would cause the issue. https://developer.jboss.org/thread/203599?tstart=0 is a related discussion. In the config you'll see:
<coordinator-environment default-timeout="300"/>
So you may need to increase that timeout.
> No active transaction found while executing long running update statement
> -------------------------------------------------------------------------
>
> Key: TEIID-4097
> URL: https://issues.jboss.org/browse/TEIID-4097
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.11.3
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
>
> When executing the following statement an exception "java.sql.SQLException: javax.resource.ResourceException: IJ000460: Error checking for a transaction" occurs
> update MVGobs set SequenceName = (select Naam from #seqUniek where ordernumber = MVGobs.OrderNumber and patientID = MVGobs.patientid) where patientid <= 60222
> The MVGObs table is a foreign temporary table on a MySQL 5.6 server. It has almost 1 million rows.
> #seqUniek is an in memory temporary table. It has a primary key defined on the combination of ordernumber and patientid. It has almost 12000 rows.
> This is the complete stack trace:
> 10:44:12,929 WARN [org.teiid.CONNECTOR] (Worker36735_QueryProcessorQueue1249945) E6abWUweBXyr Connector worker process failed for atomic-request=E6abWUweBXyr.41.2.311518: org.teiid.translator.TranslatorException: TEIID11009 java.sql.SQLException: javax.resource.ResourceException: IJ000460: Error checking for a transaction
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getConnection(JDBCExecutionFactory.java:270) [translator-jdbc-8.11.3.jar:8.11.3]
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getConnection(JDBCExecutionFactory.java:68) [translator-jdbc-8.11.3.jar:8.11.3]
> at org.teiid.translator.ExecutionFactory.getConnection(ExecutionFactory.java:194) [teiid-api-8.11.3.jar:8.11.3]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:305)
> at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source) [:1.8.0_60]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_60]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_60]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy47.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298)
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:135)
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:369)
> 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.BatchIterator.finalRow(BatchIterator.java:69)
> at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:70)
> at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:84)
> at org.teiid.common.buffer.AbstractTupleSource.hasNext(AbstractTupleSource.java:92)
> at org.teiid.query.processor.proc.ProcedurePlan.executePlan(ProcedurePlan.java:603)
> at org.teiid.query.processor.proc.CreateCursorResultSetInstruction.process(CreateCursorResultSetInstruction.java:69)
> at org.teiid.query.processor.proc.ProcedurePlan.processProcedure(ProcedurePlan.java:384)
> at org.teiid.query.processor.proc.ProcedurePlan.nextBatchDirect(ProcedurePlan.java:293)
> at org.teiid.query.processor.proc.ProcedurePlan.nextBatch(ProcedurePlan.java:267)
> at org.teiid.query.processor.relational.PlanExecutionNode.nextBatchDirect(PlanExecutionNode.java:118)
> 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.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_60]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> Caused by: java.sql.SQLException: javax.resource.ResourceException: IJ000460: Error checking for a transaction
> at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:151)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getConnection(JDBCExecutionFactory.java:266) [translator-jdbc-8.11.3.jar:8.11.3]
> ... 41 more
> Caused by: javax.resource.ResourceException: IJ000460: Error checking for a transaction
> at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:362)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:510)
> at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:143)
> ... 42 more
> Caused by: javax.resource.ResourceException: IJ000459: Transaction is not active: tx=TransactionImple < ac, BasicAction: 0:ffff7f000101:3ecd82e1:56b9cee9:3599e status: ActionStatus.ABORTED >
> at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:352)
> ... 44 more
> This is the execution plan:
> PlanExecutionNode
> Relational Node ID=4,
> Output Columns=Count (integer),
> Cost Estimates=Estimated Node Cardinality: -1.0,
> Program
> ASSIGNMENT
> Variable=VARIABLES.ROWS_UPDATED,
> Expression=0,
> LOOP
> Result Set=X,
> ProjectNode
> Relational Node ID=0,
> Output Columns=s_0 (string),s_1 (integer),s_2 (integer),
> Cost Estimates=Estimated Node Cardinality: -1.0,
> Select Columns=(SELECT #seqUniek.Naam FROM #seqUniek WHERE (#seqUniek.Ordernumber = MVGObs.Ordernumber) AND (#seqUniek.Patientid = MVGObs.Patientid) LIMIT 2) AS s_0,MVGObs.Patientid AS s_1,MVGObs.Ordernumber AS s_2,
> AccessNode
> Relational Node ID=1,
> Output Columns=Patientid (integer),Ordernumber (integer),
> Cost Estimates=Estimated Node Cardinality: -1.0,
> Query=SELECT g_0.Patientid, g_0.Ordernumber FROM MVGObs AS g_0 WHERE g_0.Patientid <= 60222,
> Model Name=tmptables,
> LimitNode
> Relational Node ID=0,
> Output Columns=Naam (string),
> Cost Estimates=Estimated Node Cardinality: 1.0,
> Row Offset=null,
> Row Limit=2,
> AccessNode
> Relational Node ID=1,
> Output Columns=Naam (string),
> Cost Estimates=Estimated Node Cardinality: 1.0,
> Query=SELECT #seqUniek.Naam FROM #seqUniek WHERE (#seqUniek.Ordernumber = MVGObs.Ordernumber) AND (#seqUniek.Patientid = MVGObs.Patientid),
> Model Name=__TEMP__,
> Program
> CREATE CURSOR
> AccessNode
> Relational Node ID=2,
> Output Columns=Count (integer),
> Cost Estimates=Estimated Node Cardinality: -1.0,
> Query=UPDATE MVGObs SET SequenceName = X.s_0 WHERE (MVGObs.Patientid = X.s_1) AND (MVGObs.Ordernumber = X.s_2),
> Model Name=tmptables,
> ASSIGNMENT
> Variable=VARIABLES.ROWS_UPDATED,
> Expression=(VARIABLES.ROWS_UPDATED + 1),
> CREATE CURSOR
> ProjectNode
> Relational Node ID=3,
> Output Columns=ROWS_UPDATED (integer),
> Cost Estimates=Estimated Node Cardinality: 1.0,
> Select Columns=VARIABLES.ROWS_UPDATED,
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (TEIID-4016) Teiid parser fails to address co-existence of SQL comment and cache hint prior to rest of SQL string
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4016?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4016.
-----------------------------------
Fix Version/s: 9.0
8.12.5
Resolution: Done
Updated the logic to look at each of the leading comments.
> Teiid parser fails to address co-existence of SQL comment and cache hint prior to rest of SQL string
> ----------------------------------------------------------------------------------------------------
>
> Key: TEIID-4016
> URL: https://issues.jboss.org/browse/TEIID-4016
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.12.4
> Reporter: Paul Richardson
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5
>
>
> Please review analysis of the issue in TEIIDDES-2802.
> In summary, when a comment is located in front of the cache hint in an sql string, the cache hint is dropped from the resulting language objects. This is due to the regular expression used for finding cache hints in the parser template.
> For Designer to fix this issue, Teiid needs to fix it as well since the results of the parsers should match, ie. there is no point in Designer retaining the cache hint if Teiid does not.
> The following unit test demonstrates this issue:
> {code}
> String sql = "/* HELLO */ /*+ cache(ttl:180000) */ SELECT col1 FROM tbl WHERE col2 IN /*+ MJ */ (SELECT col1 FROM tbl2) /* trailing comment */ ";
> String expSql = "/*+ cache(ttl:180000) */ SELECT col1 FROM tbl WHERE col2 IN /*+ MJ */ (SELECT col1 FROM tbl2) /* trailing comment */ ";
> Command command = QueryParser.getQueryParser().parseCommand(sql, new ParseInfo());
> assertEquals(expSql, command.toString()); // this will fail due to no cache hint
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (TEIID-3005) Support Kerberos pass-thru to the data source
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3005?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3005:
-------------------------------------
There is no more planned work on this JIRA. What has been asked has been delivered.
> 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)
10 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 reassigned TEIID-3005:
-------------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> 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)
10 years