Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1151027

Summary: Second connection to VDB through Kerberos authentication ends with exception
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Juraj Duráni <jdurani>
Component: TeiidAssignee: Van Halbert <vhalbert>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: dlesage, felias, mgrigull, vhalbert
Target Milestone: ER4Keywords: QA-Closed
Target Release: 6.1.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
After a successful first connection, subsequent connections to a VDB through Kerberos resulted in ajavax.security.auth.login.LoginException. To fix this problem, the cache-type="default" setting was removed. As a result, users no longer encounter this exception.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-10 08:56:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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