[JBoss JIRA] (TEIID-3803) Kerberos with ODBC with MutualAuth fails
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3803?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3803.
---------------------------------
> Kerberos with ODBC with MutualAuth fails
> ----------------------------------------
>
> Key: TEIID-3803
> URL: https://issues.jboss.org/browse/TEIID-3803
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.4
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.7.2.6_2, 8.12.2, 8.13, 8.7.6
>
>
> When Active Directory is used for Kerberos authentication, and Windows ODBC client issues connection request it may fail with following exception.
> {code}
> 00:29:15,561 ERROR [org.teiid.ODBC] (New I/O worker #19) TEIID40015 Unexpected error occurred: org.teiid.client.security.LogonException: TEIID40014 Kerberos context login failed
> at org.teiid.transport.LogonImpl.neogitiateGssLogin(LogonImpl.java:203) [teiid-runtime-8.7.4.redhat-1.jar:8.7.4.redhat-1]
> at org.teiid.odbc.ODBCServerRemoteImpl.logon(ODBCServerRemoteImpl.java:236) [teiid-runtime-8.7.4.redhat-1.jar:8.7.4.redhat-1]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_79]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_79]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_79]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_79]
> at org.teiid.transport.ODBCClientInstance.processMessage(ODBCClientInstance.java:127) [teiid-runtime-8.7.4.redhat-1.jar:8.7.4.redhat-1]
> at org.teiid.transport.ODBCClientInstance.receivedMessage(ODBCClientInstance.java:116) [teiid-runtime-8.7.4.redhat-1.jar:8.7.4.redhat-1]
> at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:211) [teiid-runtime-8.7.4.redhat-1.jar:8.7.4.redhat-1]
> at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:310) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:328) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
> Caused by: javax.security.auth.login.LoginException: TEIID50103 Wrong Response returned from teiid-security security domain; Expecting a Kerberoes response
> at org.teiid.jboss.JBossSessionService.buildGSSResult(JBossSessionService.java:138) [teiid-jboss-integration-8.7.4.redhat-1.jar:8.7.4.redhat-1]
> at org.teiid.jboss.JBossSessionService.neogitiateGssLogin(JBossSessionService.java:106) [teiid-jboss-integration-8.7.4.redhat-1.jar:8.7.4.redhat-1]
> at org.teiid.services.SessionServiceImpl.neogitiateGssLogin(SessionServiceImpl.java:545) [teiid-runtime-8.7.4.redhat-1.jar:8.7.4.redhat-1]
> at org.teiid.transport.LogonImpl.neogitiateGssLogin(LogonImpl.java:173) [teiid-runtime-8.7.4.redhat-1.jar:8.7.4.redhat-1]
> ... 30 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 1 month
[JBoss JIRA] (TEIID-4094) Move the packaging of teiid-jdbc.jar into is own project
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4094?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4094.
---------------------------------
> 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: 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
(v7.2.2#72004)
8 years, 1 month
[JBoss JIRA] (TEIID-4421) Teiid Translator per source/version
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4421?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4421.
---------------------------------
> Teiid Translator per source/version
> -----------------------------------
>
> Key: TEIID-4421
> URL: https://issues.jboss.org/browse/TEIID-4421
> Project: Teiid
> Issue Type: Feature Request
> Components: Embedded
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Fix For: 9.1
>
>
> Teiid actually uses a single translator to connect to a single source/version. However in the case of translators that auto-configure to the given version it is expected to manage creating new instances when necessary.
> Case reproduced when connecting to 2 DBs, one on SQL Server 2012 and another on SQL Server 2008. The pagination SQL translation of SQL Server 2012 does not work on 2008.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 1 month
[JBoss JIRA] (TEIID-3966) google spreadsheet translator using Collections.singletonList instance returned by the runtime doesn't support the set method.
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3966?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3966.
---------------------------------
> google spreadsheet translator using Collections.singletonList instance returned by the runtime doesn't support the set method.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-3966
> URL: https://issues.jboss.org/browse/TEIID-3966
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.6
> Reporter: Marco Ardito
> Assignee: Steven Hawkins
> Fix For: 8.13, 9.0, 8.12.5
>
>
> This arised as a follow-up of a forum thread, I tried to create a google spreadsheet dynamic VDB, exposing both the source as is, and also a model with a restricted view using only some fileds in the source model. from the sql client (squirrel) connnected to the vdb, but only the raw source model works, while any query to the view shows error
> org.teiid.core.TeiidException
> SQLState: 38000
> ErrorCode: 0
> In the thread, Steven Hawkins spotted the bug:<<The issue is that the translator is using Collections.singletonList to return the row and the engine is expecting it to be modifiable to avoid the additional copy one the value types are corrected. The SingletonList instance returned by the runtime unfortunately doesn't support the set method. >>
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 1 month
[JBoss JIRA] (TEIID-4368) Fail to deploy VDB with TextTable SELECTOR, ROW DELIMITER, HEADER
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4368?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4368.
---------------------------------
> Fail to deploy VDB with TextTable SELECTOR, ROW DELIMITER, HEADER
> -----------------------------------------------------------------
>
> Key: TEIID-4368
> URL: https://issues.jboss.org/browse/TEIID-4368
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7
> Reporter: Lucie Fabrikova
> Assignee: Steven Hawkins
> Attachments: texttabvdb-vdb.xml
>
>
> Server fails to deploy dynamic vdb with models which contain following TextTable parameters: SELECTOR, ROW DELIMITER, HEADER.
> Part of server log:
> 10:24:02,171 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "texttabvdb-vdb.xml" (runtime-name: "texttabvdb-vdb.xml")
> 10:24:02,213 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model2" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM
> 10:24:02,214 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model3" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM
> 10:24:02,217 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB texttab.1 model "model2" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "COLUMNS col1 string [*]ROW[*] DELIMITER 'X'" at line 7, column 59.
> Was expecting: "escape" | "no" | "selector" | "skip" | "width" | "delimiter" | "quote" | "header" | "," | "(" ...
> 10:24:02,218 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB texttab.1 model "model3" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered ") COLUMNS a [*]HEADER[*] 'a' string" at line 7, column 52.
> Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...
> 10:24:02,219 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB texttab.1 model "model5" metadata is currently being loaded. Start Time: 8/1/16 10:24 AM
> 10:24:02,222 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID50030 VDB texttab.1 model "model5" metadata loaded. End Time: 8/1/16 10:24 AM
> 10:24:02,298 INFO [org.jboss.as.server] (management-handler-thread - 14) JBAS015865: Replaced deployment "texttabvdb-vdb.xml" with deployment "texttabvdb-vdb.xml"
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 1 month