[
https://issues.jboss.org/browse/TEIID-2863?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2863:
-------------------------------------
There are two different scenarios. Let's say Teiid server configured is with two
security-domains one USERPWD and GSS.
case 1) User defined as preference auth type GSS, then they tried to login, if they fail,
do that automatically fallback to USERPWD?
case 2) User defined as preference auth type is GSS, if failed then auth process throws a
login exception.
so in,
case 2, we can handle similarly in jdbc/odbc based on "user" name pattern
suggestion, but not case 1, here the preference is set by user.
case 1, we can handle in jdbc but not sure there is path for odbc, as odbc needs to notify
user what auth mechanism it is going follow through and stick to it. But from what I
understand Cristinio's usecase he is looking for case 1.
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