April 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Work started: (TEIID-260) Secure RPC calls for secure services over JGroups

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-260?page=com.atlassian.jira.plug... ] Work on TEIID-260 started by Steven Hawkins. > Secure RPC calls for secure services over JGroups > ------------------------------------------------- > > Key: TEIID-260 > URL: https://jira.jboss.org/jira/browse/TEIID-260 > Project: Teiid > Issue Type: Task > Components: Server > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 6.1.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Need to add security (message level or otherwise) to RPC calls made over JGroups based upon the configuration and whether the service is secure. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-468) Remove QueryAdminApi

by Steven Hawkins (JIRA)

Remove QueryAdminApi -------------------- Key: TEIID-468 URL: https://jira.jboss.org/jira/browse/TEIID-468 Project: Teiid Issue Type: Task Components: Console, Server Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 Remove the subsystem interface in favor of adminapi. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-466) Remove product based display and logic

by Steven Hawkins (JIRA)

Remove product based display and logic -------------------------------------- Key: TEIID-466 URL: https://jira.jboss.org/jira/browse/TEIID-466 Project: Teiid Issue Type: Task Components: Console, Server Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 There is only a single product now, so there is no need for reporting product info, sessions by product, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Closed: (TEIID-329) Change sessionid to something non-guessable

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-329?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-329. -------------------------------- Resolution: Done changed back to a long session identifier. SessionToken is responsible for holding the session secret. also ensured that session tokens were not leaked to the clients in any other way than logonresult. > Change sessionid to something non-guessable > ------------------------------------------- > > Key: TEIID-329 > URL: https://jira.jboss.org/jira/browse/TEIID-329 > Project: Teiid > Issue Type: Task > Components: Server > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.1.0 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Currently the sessionid is based upon a long sequence. It is extremely easy to exploit and then hijack a session. Sessionids should instead be based upon something that is hard to guess (such as a UUID) and should also be encrypted when being returned to the server or resent from the client. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-467) Simplify DBIDGenerator logic

by Steven Hawkins (JIRA)

Simplify DBIDGenerator logic ---------------------------- Key: TEIID-467 URL: https://jira.jboss.org/jira/browse/TEIID-467 Project: Teiid Issue Type: Task Components: Server Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 DBIDGenerator should be simplified. Synchronization should be on a per block basis. It's all performed in a transaction, there's no need for looping in the db code. Also should only expose 1 method to get the next id - all others are not utilized. Finally it should more easily tested rather than by toggling a switch on the singleton. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Updated: (TEIID-329) Change sessionid to something non-guessable

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-329?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-329: --------------------------------- Fix Version/s: 6.1.0 (was: 6.0.0) > Change sessionid to something non-guessable > ------------------------------------------- > > Key: TEIID-329 > URL: https://jira.jboss.org/jira/browse/TEIID-329 > Project: Teiid > Issue Type: Task > Components: Server > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.1.0 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Currently the sessionid is based upon a long sequence. It is extremely easy to exploit and then hijack a session. Sessionids should instead be based upon something that is hard to guess (such as a UUID) and should also be encrypted when being returned to the server or resent from the client. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Reopened: (TEIID-329) Change sessionid to something non-guessable

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-329?page=com.atlassian.jira.plug... ] Steven Hawkins reopened TEIID-329: ---------------------------------- It is not sufficient to just change the session identifier. Some attempt is needed to hide the session secret to ensure that sessions cannot easily be hijacked. > Change sessionid to something non-guessable > ------------------------------------------- > > Key: TEIID-329 > URL: https://jira.jboss.org/jira/browse/TEIID-329 > Project: Teiid > Issue Type: Task > Components: Server > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.0.0 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Currently the sessionid is based upon a long sequence. It is extremely easy to exploit and then hijack a session. Sessionids should instead be based upon something that is hard to guess (such as a UUID) and should also be encrypted when being returned to the server or resent from the client. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-463) ServerAdmin bounce wait does not work

by Steven Hawkins (JIRA)

ServerAdmin bounce wait does not work ------------------------------------- Key: TEIID-463 URL: https://jira.jboss.org/jira/browse/TEIID-463 Project: Teiid Issue Type: Bug Components: Console Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 The bounce wait code in the serveradminfactory does not take into account that the initial bounce invocation should cause a communication exception. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-462) Clean up console exception handling

by Steven Hawkins (JIRA)

Clean up console exception handling ----------------------------------- Key: TEIID-462 URL: https://jira.jboss.org/jira/browse/TEIID-462 Project: Teiid Issue Type: Quality Risk Components: Console Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 The console needs more consistency in exception logging and reporting to ensure that the user messages displayed are accurate and that the log is clean. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-461) ClassCastException Executing Request on Teiid (Retrieving WSDL from Web Service VDB)

by Ted Jones (JIRA)

ClassCastException Executing Request on Teiid (Retrieving WSDL from Web Service VDB) ------------------------------------------------------------------------------------ Key: TEIID-461 URL: https://jira.jboss.org/jira/browse/TEIID-461 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.0.0 Reporter: Ted Jones Assignee: Steven Hawkins Attempting to retrieve the WSDL from a Web Service VDB, I received the following exception; Apr 03, 2009 13:48:35.785 [Worker0_RuntimeMetadataService<tejones-laptop|MMProcess|1121>0|0] ERROR <CONNECTOR|0> Connector worker process failed for atomic-request=6c7905d2-7a40-47d0-ab1b-2bb64ea79717.0.3.0 java.lang.ClassCastException: $Proxy37 cannot be cast to com.metamatrix.dqp.service.metadata.IndexSelectorSource at com.metamatrix.connector.metadata.IndexConnector.getMetadataObjectSource(IndexConnector.java:49) at com.metamatrix.connector.metadata.adapter.ObjectConnection.getMetadataObjectSource(ObjectConnection.java:67) at com.metamatrix.connector.metadata.adapter.ObjectConnection.createProcedureExecution(ObjectConnection.java:63) at org.teiid.connector.basic.BasicConnection.createExecution(BasicConnection.java:57) at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.createExecution(ConnectorWorkItem.java:310) at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.createExecution(SynchConnectorWorkItem.java:100) at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.process(ConnectorWorkItem.java:151) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44) at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.run(SynchConnectorWorkItem.java:69) at com.metamatrix.common.queue.WorkerPoolFactory$StatsCapturingSharedThreadPoolExecutor$1.run(WorkerPoolFactory.java:211) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Apr 03, 2009 13:48:35.799 [Worker1_QueryProcessorQueue1|0] ERROR <DQP|0> Unexpected exception for request 6c7905d2-7a40-47d0-ab1b-2bb64ea79717.0 [MetaMatrixComponentException]$Proxy37 cannot be cast to com.metamatrix.dqp.service.metadata.IndexSelectorSource 1 [ClassCastException]$Proxy37 cannot be cast to com.metamatrix.dqp.service.metadata.IndexSelectorSource at org.teiid.dqp.internal.process.DataTierTupleSource.switchBatch(DataTierTupleSource.java:128) at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:89) at com.metamatrix.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:127) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:247) at com.metamatrix.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:173) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:247) at com.metamatrix.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:173) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:247) at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:109) at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:151) at com.metamatrix.query.processor.proc.ProcedurePlan.getResults(ProcedurePlan.java:297) at com.metamatrix.query.processor.proc.ProcedureEnvironment.executePlan(ProcedureEnvironment.java:130) at com.metamatrix.query.processor.proc.ExecSqlInstruction.process(ExecSqlInstruction.java:93) at com.metamatrix.query.processor.proc.ProcedurePlan.processProcedure(ProcedurePlan.java:282) at com.metamatrix.query.processor.proc.ProcedurePlan.nextBatch(ProcedurePlan.java:221) at com.metamatrix.query.processor.relational.PlanExecutionNode.nextBatchDirect(PlanExecutionNode.java:106) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:247) at com.metamatrix.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:173) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:247) at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:109) at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:151) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:265) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:211) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44) at com.metamatrix.common.queue.WorkerPoolFactory$StatsCapturingSharedThreadPoolExecutor$1.run(WorkerPoolFactory.java:211) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassCastException: $Proxy37 cannot be cast to com.metamatrix.dqp.service.metadata.IndexSelectorSource at com.metamatrix.connector.metadata.IndexConnector.getMetadataObjectSource(IndexConnector.java:49) at com.metamatrix.connector.metadata.adapter.ObjectConnection.getMetadataObjectSource(ObjectConnection.java:67) at com.metamatrix.connector.metadata.adapter.ObjectConnection.createProcedureExecution(ObjectConnection.java:63) at org.teiid.connector.basic.BasicConnection.createExecution(BasicConnection.java:57) at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.createExecution(ConnectorWorkItem.java:310) at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.createExecution(SynchConnectorWorkItem.java:100) at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.process(ConnectorWorkItem.java:151) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44) at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.run(SynchConnectorWorkItem.java:69) ... 4 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2009