[JBoss JIRA] (TEIID-2247) API changes in point release
by Paul Richardson (JIRA)
Paul Richardson created TEIID-2247:
--------------------------------------
Summary: API changes in point release
Key: TEIID-2247
URL: https://issues.jboss.org/browse/TEIID-2247
Project: Teiid
Issue Type: Bug
Affects Versions: 8.2
Reporter: Paul Richardson
Assignee: Steven Hawkins
Fix For: 8.2
Updated teiid designer 8.0 (unreleased) to 8.2.Alpha2 jars.
API changes have occurred between 8.1 and 8.2. Are the following changes essential and could they be reverted and deprecated until 9.0?
* org.teiid.query.sql.proc.RaiseErrorStatement renamed to org.teiid.query.sql.proc.RaiseStatement
* org.teiid.core.TeiidRuntimeException
** Constructor(String, String) visibility narrowed
** Constructor(Exception, String) removed
* org.teiid.query.sql.proc.CreateProcedureCommand
* Removal of getResultsCommand() method
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIID-2269) Support securing ssl keystore password via VAULT at jdbc/odbc transport
by Jack Ma (JIRA)
Jack Ma created TEIID-2269:
------------------------------
Summary: Support securing ssl keystore password via VAULT at jdbc/odbc transport
Key: TEIID-2269
URL: https://issues.jboss.org/browse/TEIID-2269
Project: Teiid
Issue Type: Feature Request
Components: JDBC Connector, ODBC
Affects Versions: 8.1
Reporter: Jack Ma
Assignee: Steven Hawkins
Failed to set up the ssl at teiid jdbc transport layer by using JBOSS vault to secure ssl keystore password:
Here is the detail I did at my failure tests:
At first, create my vault and ading folowing section into standalone-teiid.xmlt:
<vault>
<vault-option name="KEYSTORE_URL" value="c:\\vault\\vault.keystore"/>
<vault-option name="KEYSTORE_PASSWORD" value="MASK-CGClE.QFRs1"/>
<vault-option name="KEYSTORE_ALIAS" value="vault"/>
<vault-option name="SALT" value="12345678"/>
<vault-option name="ITERATION_COUNT" value="50"/>
<vault-option name="ENC_FILE_DIR" value="c:\\vault\\"/>
</vault>
Here is the SSL definition for teiid JDBC tranport at standalone-teiid.xml
<transport name="jdbc" socket-binding="teiid-jdbc">
<ssl mode="enabled" keymanagement-algorithm="SunX509">
<keystore name="c:\\vault\\test.keystore" password="${VAULT::keystore_pw::PASSWORD::ZWQxMWNiMzktOThmNS00NWIyLWFjZTUtNmExYWFiNzUyOTk5TElORV9CUkVBS3ZhdWx0}"/>
</ssl>
</transport>
Here is the error log:
09:40:55,750 WARNING [org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink] (New I/O server boss #1 ([id: 0x00175b9a, /0.0.0.0:31050])) Failed to initialize an accepted socket.: java.io.IOException: Keystore was tampered with, or password was incorrect
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:771) [rt.jar:1.6.0_34]
at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38) [rt.jar:1.6.0_34]
at java.security.KeyStore.load(KeyStore.java:1185) [rt.jar:1.6.0_34]
at org.teiid.net.socket.SocketUtil.loadKeyStore(SocketUtil.java:221) [teiid-client-8.2.0.Beta1.jar:8.2.0.Beta1]
at org.teiid.net.socket.SocketUtil.getSSLContext(SocketUtil.java:171) [teiid-client-8.2.0.Beta1.jar:8.2.0.Beta1]
at org.teiid.transport.SSLConfiguration.getServerSSLEngine(SSLConfiguration.java:76) [teiid-runtime-8.2.0.Beta1.jar:8.2.0.Beta1]
at org.teiid.transport.SSLAwareChannelHandler.getPipeline(SSLAwareChannelHandler.java:228) [teiid-runtime-8.2.0.Beta1.jar:8.2.0.Beta1]
at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink$Boss.registerAcceptedChannel(NioServerSocketPipelineSink.java:276) [netty-3.2.6.Final.jar:]
at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink$Boss.run(NioServerSocketPipelineSink.java:246) [netty-3.2.6.Final.jar:]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_34]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_34]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_34]
Caused by: java.security.UnrecoverableKeyException: Password verification failed
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:769) [rt.jar:1.6.0_34]
... 11 more
In side the debug, it looks like teiid did not substitude password from the vault keystore at all. It uses password string "${VAULT::keystore_pw::PASSWORD::ZWQxMWNiMzktOThmNS00NWIyLWFjZTUtNmExYWFiNzUyOTk5TElORV9CUkVBS3ZhdWx0}" to access keystore directly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIID-2217) Create metadata processor to expose the object metadata for dynamic vdbs
by Van Halbert (JIRA)
Van Halbert created TEIID-2217:
----------------------------------
Summary: Create metadata processor to expose the object metadata for dynamic vdbs
Key: TEIID-2217
URL: https://issues.jboss.org/browse/TEIID-2217
Project: Teiid
Issue Type: Sub-task
Components: Misc. Connectors
Affects Versions: 8.2
Reporter: Van Halbert
Assignee: Steven Hawkins
A metadata processor needs to be created to expose the object metadata based on the class or classes indicated that are accessible by querying the cache. There will be 2 processors created based on: 1) the getters (when annotations is not being used) and 2) based on annotations. The result of the metadata will be a view that uses the OBECTABLE.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIID-2278) Restarting server causes NPE when reading metadata for the vdb that uses 'ws' translator
by Van Halbert (JIRA)
Van Halbert created TEIID-2278:
----------------------------------
Summary: Restarting server causes NPE when reading metadata for the vdb that uses 'ws' translator
Key: TEIID-2278
URL: https://issues.jboss.org/browse/TEIID-2278
Project: Teiid
Issue Type: Bug
Components: XML Connector
Affects Versions: 8.2
Reporter: Van Halbert
Assignee: Steven Hawkins
Attachments: twitter-ds.xml, twitter-vdb.xml
Running the twitter quick start and when server is restarted, the following stacks trace is produced:
13:04:27,756 ERROR [org.jboss.threads.executor] (teiid-async-threads - 4) Task execution failed for task org.teiid.jboss.VDBService$6@15d0ff7: java.lang.NullPointerException
at org.teiid.query.metadata.MetadataValidator.addColumn(MetadataValidator.java:295) [teiid-engine-8.2.0.CR1-SNAPSHOT.jar:8.2.0.CR1-SNAPSHOT]
at org.teiid.query.metadata.MetadataValidator.validate(MetadataValidator.java:240) [teiid-engine-8.2.0.CR1-SNAPSHOT.jar:8.2.0.CR1-SNAPSHOT]
at org.teiid.query.metadata.MetadataValidator.access$000(MetadataValidator.java:63) [teiid-engine-8.2.0.CR1-SNAPSHOT.jar:8.2.0.CR1-SNAPSHOT]
at org.teiid.query.metadata.MetadataValidator$ResolveQueryPlans.execute(MetadataValidator.java:183) [teiid-engine-8.2.0.CR1-SNAPSHOT.jar:8.2.0.CR1-SNAPSHOT]
at org.teiid.query.metadata.MetadataValidator.validate(MetadataValidator.java:73) [teiid-engine-8.2.0.CR1-SNAPSHOT.jar:8.2.0.CR1-SNAPSHOT]
at org.teiid.deployers.VDBRepository.finishDeployment(VDBRepository.java:289) [teiid-runtime-8.2.0.CR1-SNAPSHOT.jar:8.2.0.CR1-SNAPSHOT]
at org.teiid.runtime.AbstractVDBDeployer.metadataLoaded(AbstractVDBDeployer.java:170) [teiid-runtime-8.2.0.CR1-SNAPSHOT.jar:8.2.0.CR1-SNAPSHOT]
at org.teiid.jboss.VDBService.access$900(VDBService.java:91) [teiid-jboss-integration-8.2.0.CR1-SNAPSHOT.jar:8.2.0.CR1-SNAPSHOT]
at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.2.0.CR1-SNAPSHOT.jar:8.2.0.CR1-SNAPSHOT]
at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:801)
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:821)
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_35]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
If I clean the data/teiid-data directory and restart, its ok, but restart again, NPE is produced again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIID-2275) Convert dynamicvdb-twitter to a quickstart
by Van Halbert (JIRA)
Van Halbert created TEIID-2275:
----------------------------------
Summary: Convert dynamicvdb-twitter to a quickstart
Key: TEIID-2275
URL: https://issues.jboss.org/browse/TEIID-2275
Project: Teiid
Issue Type: Sub-task
Components: Build/Kits
Affects Versions: 8.2
Reporter: Van Halbert
Assignee: Van Halbert
Convert the dynamicvdb-twitter into a quick start, which will provide a means such that a user can auto configure and deploy artifacts to a jboss-as server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIID-2276) Change simpleclient quickstart to pass in username/password instead of hard coding
by Van Halbert (JIRA)
Van Halbert created TEIID-2276:
----------------------------------
Summary: Change simpleclient quickstart to pass in username/password instead of hard coding
Key: TEIID-2276
URL: https://issues.jboss.org/browse/TEIID-2276
Project: Teiid
Issue Type: Enhancement
Components: Build/Kits
Affects Versions: 8.2
Reporter: Van Halbert
Assignee: Van Halbert
Priority: Minor
Change JDBCClient.java to accept username/password via system properties. This will also change the run.sh(bat) scripts to pass in the properties. This should be done so that other quick starts can easily use different username/passwords for demonstrations without having to recompile the class.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months