[
https://issues.jboss.org/browse/TEIID-2863?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2863:
---------------------------------------
Could the approach be to use a vdb property to determine if gss authentication should be
forced? We could even leave the krb5-domain property and let it be a boolean to be the
transport wide default. Then we wouldn't have to use a naming convention for the
security-domain.
It looks like the user/database should be sent with ODBC initialize, so this should be
possible with both JDBC and ODBC.
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