Chapter 5. Configuring Transport Security

5.1. Transport Security Configuration

There are three types of direct remote transports, each with its own encryption configuration:
  • teiid - By default, this only encrypts login traffic when none of the other configuration properties are used.
  • odbc - This default to "no SSL".
  • odata
Here is an example OData transport configuration: 
<transport name="jdbc" socket-binding="teiid-jdbc" protocol="teiid">
      <authentication security-domain="teiid-security"/>
</transport>
<transport name="odbc" socket-binding="teiid-odbc" protocol="pg">
     <authentication security-domain="teiid-security"/>
     <ssl mode="disabled"/>
</transport>
Here is a configuration for OData: 
<transport name="odata">
   <authentication security-domain="teiid-security"/>
</transport>

Note

The pg protocol for ODBC access uses cleartext username and password authentication by default. You should consider using a security domain that utilizes non-plaintext passwords, kerberos, or SSL.
The SSL configuration is part of the transport configuration in the Teiid subsystem.
Other indirect methods of access to the Teiid subsystem rely on the container settings for HTTP/HTTPS access.