[
https://issues.jboss.org/browse/TEIID-2863?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2863:
-------------------------------------
Yes, I added "authentication-type" to the VDB as well. I send a pull request,
you can review. I will keep the JIRA open for any further changes.
* SSL, right now "is SSL required" is the only flag that comes from client, rest
of the configuration comes from transport, don't we do similar functionality when
"mms" is present in the JDBC url?
* Is this a new property? I remember Teiid has functionality some where? May be it was on
CXF config, or somebody may asked in forums. If yes, then may be we will do separate JIRA
for this functionality.
* Previously I ignored the Principal returned from GSS auth, thus we had both connection
supplied user and GSS principal. Now I am using GSS principle as the user logging into
Teiid. I do not think I follow your question about match/map the user names one from
other? Do you see any particular need for this?
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