[teiid-issues] [JBoss JIRA] (TEIID-2260) Teiid 8.X ODBC port does not follow security settings

[Graeme Gillies (JIRA)]

Graeme Gillies created TEIID-2260:
-------------------------------------

             Summary: Teiid 8.X ODBC port does not follow security settings
                 Key: TEIID-2260
                 URL: https://issues.jboss.org/browse/TEIID-2260
             Project: Teiid
          Issue Type: Bug
          Components: ODBC
    Affects Versions: 8.2
         Environment: Red Hat Enterprise Linux Server release 6.3 (Santiago)
java version "1.7.0_05-icedtea"
OpenJDK Runtime Environment (rhel-2.2.1.el6_3.3-x86_64)
OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode)
jbossas-standalone-7.1.2-8.Final_redhat_1.ep6.el6.noarch (JBoss EAP 6)
            Reporter: Graeme Gillies
            Assignee: Steven Hawkins


Hi,

We have the following configuration setup in our teiid 8.2 aplha 2 environment running on eap6
{noformat}
            <transport name="jdbc" socket-binding="teiid-jdbc">
                <authentication security-domain="REDHAT.COM"/>
                <ssl mode="enabled" ssl-protocol="SSLv3" keymanagement-algorithm="SunX509">
                    <keystore name="/etc/jbossas/standalone/jboss.keystore" password="changeit"/>
                </ssl>
            </transport>
            <transport name="odbc" socket-binding="teiid-odbc" protocol="pg">
                <authentication security-domain="REDHAT.COM"/>
                <ssl mode="enabled" ssl-protocol="SSLv3" keymanagement-algorithm="SunX509">
                    <keystore name="/etc/jbossas/standalone/jboss.keystore" password="changeit"/>
                </ssl>
            </transport>
{noformat}

With out security configuration looking like

{noformat}
                <security-domain name="host" cache-type="default">
                    <authentication>
                        <login-module code="Kerberos" flag="required">
                            <module-option name="storeKey" value="true"/>
                            <module-option name="useKeyTab" value="true"/>
                            <module-option name="principal" value="HTTP/REMOVED_HOSTNAME at REDHAT.COM"/>
                            <module-option name="keyTab" value="/etc/jbossas/standalone/jboss.keytab"/>
                            <module-option name="doNotPrompt" value="true"/>
                            <module-option name="debug" value="true"/>
                        </login-module>
                    </authentication>
                </security-domain>
                <security-domain name="fallback" cache-type="default">
                    <authentication>
                        <login-module code="Kerberos" flag="required">
                            <module-option name="useTicketCache" value="true"/>
                            <module-option name="useKeyTab" value="false"/>
                            <module-option name="doNotPrompt" value="true"/>
                            <module-option name="debug" value="true"/>
                        </login-module>
                    </authentication>
                </security-domain>
                <security-domain name="REDHAT.COM" cache-type="default">
                    <authentication>
                        <login-module code="SPNEGO" flag="requisite">
                            <module-option name="password-stacking" value="useFirstPass"/>
                            <module-option name="serverSecurityDomain" value="host"/>
                            <module-option name="removeRealmFromPrincipal" value="true"/>
                            <module-option name="usernamePasswordDomain" value="fallback"/>
                        </login-module>
                    </authentication>
                </security-domain>
{noformat}

And the security seems to work as expected for the JDBC connection, but when we try to connect via ODBC to port 35432 it simply allows us to connect regardless of any username/password combination we use. We tried even switching back to just basic username/password login module (against flat files) with same results.

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