Bug 1151027 - Second connection to VDB through Kerberos authentication ends with exception
Summary: Second connection to VDB through Kerberos authentication ends with exception
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid
Version: 6.1.0
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ER4
: 6.1.0
Assignee: Van Halbert
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-09 12:48 UTC by Juraj Duráni
Modified: 2016-02-10 08:56 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-02-10 08:56:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-3164 0 Major Closed Second connection to VDB through Kerberos authentication ends with exception 2019-05-27 08:09:28 UTC

Description Juraj Duráni 2014-10-09 12:48:23 UTC
Second (third,forth,...) conection to VDB through Kerberos ends with exception:
javax.security.auth.login.LoginException: TEIID50103 Wrong Response returned from EXAMPLE.COM security domain; Expecting a Kerberoes response

Steps to reproduce:

1. Comfigure Kerberos authentication with Teiid over JDBC (https://developer.jboss.org/wiki/APracticalhow-toGuideToKerberosAuthenticationWithTeiidOverJDBC)
  - do not set default Kerberos authentication for teiid-jdbc port:
<transport name="jdbc" socket-binding="teiid-jdbc" protocol="teiid">
    <authentication security-domain="teiid-security"/>
</transport>

2. Create dynamic VDB and add required properties to define Kerberos authentication (https://docs.jboss.org/author/display/teiid88final/Kerberos+support+through+GSSAPI)
3. Connect to VDB and run any query (e.g. SELECT VDBName FROM SYS.Schemas)
4. First attempt should return correct result
5. Second ends with exception

Comment 1 JBoss JIRA Server 2014-10-16 20:45:50 UTC
Ramesh Reddy <rareddy> updated the status of jira TEIID-3164 to Resolved

Comment 2 Juraj Duráni 2014-11-26 14:54:08 UTC
According to jira TEIID-3164 the solution is to remove the cache-type="default" setting.

Comment 3 JBoss JIRA Server 2015-10-08 14:39:57 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-3164 to Closed


Note You need to log in before you can comment on or make changes to this bug.