[
https://issues.jboss.org/browse/TEIID-2863?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2863:
----------------------------------
Attachment: auth.patch
What about something like the attached? This would avoid the notion of an ANY
authentication type and allows the vdb to override all settings related to authentication.
We also need a compatibility issue in the release notes as we are only supporting a single
security domain on the transport setting. But from what I can see with
JBossSessionService if there is only a single security domain set on the transport, then
that is the only one the service will know about. Setting a different security domain in
a vdb seems like it will fail.
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
Attachments: auth.patch
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