此内容没有您所选择的语言版本。
5.2. Transport Security Properties
The following properties can be set when defining the transport security setting for a transport.
| Setting | Description | Default Value |
|---|---|---|
| mode |
Options are:
disabled, login, or enabled.
If set to
disabled, no transport or message level encryption will be used.
If set to
login, only the login traffic will be encrypted at a message level using 128 bit AES with an ephemeral DH key exchange. This only applies to the teiid transport. (No other configuration values are required in this mode.)
If set to
enabled, traffic will be encrpyted using SSL according to the configuration properties below. teiid transport clients must connect using SSL with the mms protocol. ODBC pg transport clients may optionally use SSL.
| login |
| keystore/name | The filename of the keystore that contains the private key of the server. The file name can be specified relative to the JBoss Data Virtualization deployer classloader or by absolute file system path. A typical installation would place the keystore file in the EAP_HOME/MODE/configuration directory. | cert.keystore |
| keystore/password | The password used to access the keystore. | |
| keystore/type | The keystore type created by the keytool. | JKS |
| keystore/key-alias | The keystore key-alias created by the keytool. | |
| ssl-protocol | Type of SSL protocol to be used. | TLSv1 |
| keymanagement-algorithm | Type of key algorithm to be used. | |
| truststore/name | If authentication-mode is set to 2-way, this property must be provided. This is the truststore that contains the public key for the client. Depending on how you created the keystore and truststores, this may be the same as the file specified for keystore/name. | cert.truststore |
| truststore/password | The password used to access the truststore. | |
| authentication-mode | Options are 1-way, 2-way and anonymous. | 1-way |
| enabled-cipher-suites | A comma separated list of cipher suites allowed for encryption between the client and server. The values must be supported by the JVM, otherwise the SSL connections will fail.
Note
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. Administrators can restrict the cipher suites used for encryption by setting the enabled-cipher-suites property.
| This defaults to all supported cipher suites for the virtual machine. |
Note
You will typically use the CLI to modify the transport configuration.
Warning
Red Hat recommends to encrypt passwords in production systems. Refer to the JBoss Enterprise Application Platform Security Guide for information about the Password Vault.
