Encryption Modes

Teiid supports a couple different levels Encryption based on the "mode" attribute on "ssl" element which is part of "transport" configuration in the Teiid subsystem.

• logIn - (non-data) messages between client and server are encrypted using a Diffy-Hellman key that is negotiated per connection. This is default setting for JDBC connections that use "teiid" transport.

• enabled - Mode to enable certificate based SSL

• disabled - turns off any kind of encryption

SSL Authentication Modes

• anonymous – No certificates are required, but all communications are still encrypted using the TLS_DH_anon_WITH_AES_128_CBC_SHA SSL suite. In most secure intranet environments, anonymous is suitable to just bulk encrypt traffic without the need to setup SSL certificates. No certificates are exchanged, settings are not needed for the keystore and truststore properties. Clients must have org.teiid.ssl.allowAnon set to true (the default) to connect to an anonymous server.

• 1-way – Only authenticates the server to the client. Requires a private key keystore to be created for the server and a truststore at the client that authenticates that certificate.

• 2-way – Mutual client and server authentication. The server and client applications each have a keystore for their private keys and each has a truststore that authenticates the other. The server will present a certificate, which is obtained from the keystore related properties. The client should have a truststore configured to accept the server certificate. The client is also expected to present a certificate, which is obtained from its keystore. The client certificate should be accepted by the trust store configured by the truststore related properties.

For non-anonymous SSL, the suite is negotiated - see enabled-cipher-suites below below.

Depending upon the SSL mode, follow the guidelines of your organization around creating/obtaining private keys. If you have no organizational requirements, then follow this guide to create self-signed certificates with their respective keystores and truststores. The following keystore and truststore combinations are required for different SSL modes. The names of the files can be chosen by the user. The following files are shown for example purposes only.

1-way

1. server.keystore - has server's private key
2. server.truststore - has server's public key

2-way

1. server.keystore - has server's private key
2. server.truststore - has server's public key
3. client.keystore - client's private key
4. client.truststore - has client's public key

Full Configuration Options

There are two types of remote transports, each with it's own SSL configuration:

• "teiid" - Defaults to only encrypt login traffic, in which none of the other properties are used.
• "pg" - Defaults to no SSL

  The pg transport for ODBC access defaults to clear text username password authentication

<ssl mode="enabled" authentication-mode="1-way" ssl-protocol="SSLv3" keymanagement-algorithm="algo"
         enabled-cipher-suites="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA">
            <keystore name="cert.keystore" password="passwd" type="JKS" key-alias="alias"/>
            <truststore name="cert.truststore" password="passwd"/>
</ssl>

Properties

• mode - diabled|login|enabled
  disabled = no transport or message level security will be used.
  login = only the login traffic will be encrypted at a message level using 128 bit AES with an ephemeral DH key exchange. Only applies to the 'teiid' transport and no other config values are needed in this mode.
  enabled = traffic will be secured with SSL using the other configuration properties.

• ssl-protocol- Type of SSL protocol to be used. Default is TLSv1

• keystore/type - Keystore type created by the keytool. Default "JKS" is used.

• authentication-mode - anonymous|1-way|2-way, Type of SSL Authentication Mode.

• keymanagement-algorithm - Type of key algorithm used. Default is based upon the VM, i.e. "SunX509"

• keystore/name - The file name of the keystore, which contains the private key of the Server. The file name can be relative resource path available to the Teiid deployer classloader or an absolute file system path. A typical installation would place the keystore file in the conf directory of the profile where Teiid is deployed with a file name relative to the conf path.

• keystorePassword - password for the keystore.

• keystore/key-alias - Alias name for the certificate that is in the key store.

• truststore/name - if "authenticationMode" is chosen as "2-way", then this property must be provided. This is the truststore that contains the public key for the client. Depending upon how you created the keystore and truststores, this may be same file as defined under "keystoreFilename" property.

• truststore/password - password for the truststore.

• enabled-cipher-suites - A comma separated list of cipher suites allowed for encryption between server and client. The values must be valid supported cipher suites otherwise SSL connections will fail.

You will typically use the CLI to modify the transport configuration.

If you do not like to leave clear text passwords in the configuration file, then you can use JBoss AS vault mechanism for storing the keystore and truststore passwords. Use the directions defined here https://community.jboss.org/docs/DOC-17248

Encryption Strength

Both anonymous SSL and login only encryption are configured to use 128 bit AES encryption by default. By default 1-way and 2-way SSL allow for cipher suite negotiation based upon the default cipher suites supported by the respective Java platforms of the client and server. Users can restrict the cipher suites used by specifying the enabled-cipher-suites property above in the SSL configuration.