[
https://issues.jboss.org/browse/TEIID-2863?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2863:
---------------------------------------
Putting authentication-type as a vdb property would be good as well. Looking at the
postgres configuration -
http://www.postgresql.org/docs/9.1/static/auth-pg-hba-conf.html
it's much more fine grained (acts through precedence and down to a user/host level)
than we're dealing with.
It seems like we could add transport/vdb.xml options for:
- if ssl is required (would work on a vdb basis for ODBC, already works on a transport
basis for JDBC)
- allowable hosts
- and since the kerberos username overrides the user name sent in the connection, could we
just use either a well known name or pattern to match the initial incoming user name to a
kerberos authentication
Allow both gssapi and username/password authentication on the same
transport
----------------------------------------------------------------------------
Key: TEIID-2863
URL:
https://issues.jboss.org/browse/TEIID-2863
Project: Teiid
Issue Type: Enhancement
Components: Server
Reporter: Steven Hawkins
Assignee: Steven Hawkins
With GSSAPI support enabled, username/password support on the same transport is
effectively disabled. JDBC/ODBC should ideally support both on the same transport.
--
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