84e48d0323
In summary, changes are: 1) If you have chosen MySQL, Makefile.PL will ask you if you want TLS (default: "no"), and then the locations for CA cert, client cert and client key (reasonable defaults are provided). Settings <tls>, <ca>, <cert> and <key> are added in koha-conf.xml 2) If <tls>yes</tls> in koha-conf.xml, the installer and database connection scripts add the TLS options in both DBI connection strings and mysql command line To test 1/ Apply patch 2/ Check everything still works and db connections are the same as before 3/ Either run Makefile.PL and step through the options or edit your koha-conf.xml to enable TLS 4/ Check db connections are still working Patch provided to me by Dimitris Kamenopoulos and I reformatted it into a git patch, any errors are probably mine Signed-off-by: Mirko Tietgen <mirko@abunchofthings.net> Signed-off-by: Jonathan Druart <jonathan.druart@bugs.koha-community.org> Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com> |
||
|---|---|---|
| .. | ||
| pazpar2 | ||
| searchengine | ||
| zebradb | ||
| koha-conf.xml | ||
| koha-httpd.conf | ||
| log4perl.conf | ||
| README.txt | ||
| SIPconfig.xml | ||
Koha Configuration Files: The following files specify the base configuration for Koha ZOOM: * koha-httpd.conf In a debian system, this apache configuration file will be symlinked from /etc/apache2/sites-enabled Specify Koha's IP address with NameVirtualHost Set ServerName, etc * koha-production.xml * koha-testing.xml These are the production and testing configurations for zebrasrv and for Koha. The first part of each file specifies Zebra server names, indexing configuration files, and query language configurations. Koha configuration directives follow. * zebra-authorities.cfg * zebra-biblios.cfg