[ https://issues.jboss.org/browse/TEIID-1610?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1610: --------------------------------------- Looks great. Do you mean "if (!Boolean.True.equals(result.getProperty(ILogon.KRB5_ESTABLISHED)))" in ODBCServerRemoteImpl? Seems like it could be null and we only want to continue if not established. Also I was thinking that depending upon how many calls are needed for authentication we may want to only pass the full connection properties in ILogon.logon and then not pass them for the negotiation call. That would just require having a placeholder for them on the server side. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1610?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1610: --------------------------------------- Did you try the PG 8.4 JDBC driver in GSSAPI mode? That should at least confirm the protocol. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1610?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-1610. --------------------------------- Resolution: Done JDBC was tested successfully about a couple weeks ago, there has not been any changes in the JDBC layer since then. We have seen other issues like 2011-11-29 08:49:11,562 ERROR [org.teiid.SECURITY] (New I/O server worker #1-1) Kerberos context login failed GSSException: Failure unspecified at GSS-API level (Mechanism level: Checksum failed) at sun.security.jgss.krb5.Krb5Context.acceptSecContext(Krb5Context.java:757) but, believe these are due to either DES encryption is set to false on the Active directory, or some other configuration mismatch. In either case, this is external to the Teiid, so marking as resolved. One issue still unresolved is, how JDBC client can use the cached credentials of the logged in user? I have not found any documents/information on this, so this can be further extension to the GSS API support, which needs to be tracked with separate JIRA. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira