manual:appendix:install:db_encrypt

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:appendix:install:db_encrypt [2021/01/27 20:27]
127.0.0.1 external edit
manual:appendix:install:db_encrypt [2021/05/18 13:24]
marinagen fixing a typo
Line 37: Line 37:
 A secure connection to the database can be configured during frontend installation: ​ A secure connection to the database can be configured during frontend installation: ​
   * Mark the //Database TLS encryption//​ checkbox in the [[:​manual/​installation/​frontend#​configure_db_connection|Configure DB connection]] step to enable transport encryption. ​   * Mark the //Database TLS encryption//​ checkbox in the [[:​manual/​installation/​frontend#​configure_db_connection|Configure DB connection]] step to enable transport encryption. ​
-  * Mark the //Verify database certificate//​ checkbox that appears when //TLS encryption//​ field is checked to enable ​encryptiion ​with certificates.+  * Mark the //Verify database certificate//​ checkbox that appears when //TLS encryption//​ field is checked to enable ​encryption ​with certificates.
  
 <​note>​ For MySQL, the //Database TLS encryption//​ checkbox is disabled, if //Database host// is set to localhost, because connection that uses a socket file (on Unix) or shared memory (on Windows) cannot be encrypted. \\ For PostgreSQL, the //TLS encryption//​ checkbox is disabled, if the value of the //Database host// field begins with a slash or the field is empty. </​note>​ <​note>​ For MySQL, the //Database TLS encryption//​ checkbox is disabled, if //Database host// is set to localhost, because connection that uses a socket file (on Unix) or shared memory (on Windows) cannot be encrypted. \\ For PostgreSQL, the //TLS encryption//​ checkbox is disabled, if the value of the //Database host// field begins with a slash or the field is empty. </​note>​
Line 55: Line 55:
 == Use cases == == Use cases ==
  
-Zabbix frontend uses GUI interface to define possible options: required, verify_ca, verify_full. Specify required options in the installtion ​wizard step //Configure DB connections//​. These options are mapped to the configuration file (zabbix.conf.php) in the following manner:+Zabbix frontend uses GUI interface to define possible options: required, verify_ca, verify_full. Specify required options in the installation ​wizard step //Configure DB connections//​. These options are mapped to the configuration file (zabbix.conf.php) in the following manner:
  
 ^GUI settings^Configuration file^Description^Result^ ^GUI settings^Configuration file^Description^Result^