[
https://issues.jboss.org/browse/TEIID-3177?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-3177.
-----------------------------------
Fix Version/s: 8.9
Resolution: Done
I decided that it was worthwhile to make the transports consistent. That is if the ssl
mode is set to enabled on either, that means that the client is allowed to use SSL. Also
the login setting for the ODBC ssl configuration is taken to mean that a secure
authentication mechanism is needed - which effectively requires GSS.
This is a behavioral change though. The old behavior can be utilized by setting the
system property org.teiid.ODBCRequireSecure to false.
Alternatively the configuration can be updated so that the SSL configuration for the PG
transport is explicitly disabled.
Enforce SSL connections over ODBC when Encryption Mode is enabled
-----------------------------------------------------------------
Key: TEIID-3177
URL:
https://issues.jboss.org/browse/TEIID-3177
Project: Teiid
Issue Type: Feature Request
Components: ODBC
Affects Versions: 8.8
Reporter: Cristiano Nicolai
Assignee: Steven Hawkins
Priority: Critical
Fix For: 8.9
When connecting via ODBC transport, even if the encryption mode is set to enabled is
still possible to establish non ssl connections. This allows clients to connect via
insecure method. We would like that the Teiid transport could reject connections if they
are not properly set up using SSL transport.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)