Property | Description |
|---|---|
Connection Name | Name of the connection. Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -, Maximum length is 255 characters. |
Description | Description of the connection. Maximum length is 4000 characters. |
Use Secret Vault | Stores sensitive credentials for this connection in the secrets manager that is configured for your organization. This property appears only if secrets manager is set up for your organization. When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured. Note: If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option. For information about how to configure and use a secrets manager, see Secrets manager configuration. |
Runtime Environment | The name of the runtime environment where you want to run the tasks. |
User Name | User name for the database login. The user name can't contain a semicolon. |
Password | Password for the database login. The password can't contain a semicolon. |
Host | Name of the machine that hosts the database server. |
Port | Network port number used to connect to the database server. Default is 3306. |
Database Name | Name of the MySQL database that you want to connect to. Note: The database name is case-sensitive. Maximum length is 64 characters. Database name can contain alphanumeric and underscore characters. |
Code Page | The code page of the database server. |
Use SSL | SSL attribute. Determines whether the Secure Agent establishes a secure connection to the MySQL database. When you select this option and the database server supports SSL, the Secure Agent establishes an encrypted connection. If the MySQL database server cannot configure SSL, the connection either fails or the Secure Agent establishes an unencrypted connection depending on whether you select Require SSL. If you do not select Use SSL, the Secure Agent attempts to establish an unencrypted connection. |
Verify Server Certificate | SSL attribute. If you select both Use SSL and Verify Server Certificate, the client validates the server certificate that the database server sends. |
Require SSL | SSL attribute. Applicable only if you selected Use SSL. If you select the Require SSL checkbox, and the MySQL database supports SSL, the Secure Agent establishes an SSL connection. If you select the Require SSL checkbox, and the MySQL database cannot configure SSL, the Secure Agent attempts to establish an SSL connection but fails. If you clear the Require SSL checkbox, and the MySQL database cannot configure SSL, the Secure Agent establishes an unencrypted connection. |
TLS Protocols | SSL attribute. Applicable only if you selected Use SSL. The TLS protocols used for secure communication. You can select the following protocols:
|
Trust Certificate Key Store | JDBC attribute. The path and file name of the truststore file. You must prefix the file path with file colon (file:). For example, file:C:\SSL\mysql_new\truststore |
Trust Certificate Key Store Password | JDBC attribute. The password for the truststore file. |
Client Certificate Key Store | JDBC attribute. The path and file name of the keystore file. You must prefix the file path with file colon (file:). For example, file:C:\SSL\mysql_new\keystore |
Client Certificate Key Store Password | JDBC attribute. The password to access the keystore file. |