[teiid-issues] [JBoss JIRA] (TEIID-2863) Allow both gssapi and username/password authentication on the same transport

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12948740#comment-12948740 ] 

Steven Hawkins commented on TEIID-2863:
---------------------------------------

In my list I'm talking about possible transport level enhancements to possibly get at better vdb level configuration.

> 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?

Currently SSL is requested by ODBC clients.  I'm saying that we can offer the ability to require SSL (at the transport or vdb level).  For JDBC we either require SSL or there is no SSL and this is at the transport level with no ability to configure per vdb.

> Is this a new property? I remember Teiid has functionality some where?

Yes I'm saying that it would be a new property.  Again with per vdb configurability.

>  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?

Based upon the old code I was saying that if the user name was effectively ignored anyway, then couldn't that be used to determine if gss authentication is desired?  

If however that user name is going to be used, then it's difficult to go down that path.

                
> 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