Differences

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

Link to this comparison view

knowledge-base:database-migration:ispirer-toolkit-faq:postgresql-ssl-connection [2020/06/12 10:53]
knowledge-base:database-migration:ispirer-toolkit-faq:postgresql-ssl-connection [2023/11/27 13:29] (current)
Line 1: Line 1:
 +\\
 +[[https://​www.ispirer.com|Ispirer Website]]
 +[[https://​www.ispirer.com/​products/​postgresql-migration|Ispirer Capabilities:​ PostgreSQL Migration]]
 +[[https://​www.ispirer.com/​download/​download-demo|Free Trial]]
 +====== How to Connect to PostgreSQL Using SSL ======
  
 +When migrating your source database into PostgreSQL you may need to have a possibility to connect to the target database using SSL connection.
 +For that purpose Ispirer SQLWays Wizard has a set of options that allows to use SSL connection.
 +
 +===== SSL Options =====
 +
 +To be able to connect to the target PostgreSQL database using SSL you need to set SSL options that located on the "​Advanced"​ window, on the "​Target Options"​ page:
 +
 +{{:​knowledge-base:​database-migration:​ispirer-toolkit-faq:​pg_with_ssl_1.jpg?​nolink|}}
 +\\
 +\\
 +{{:​knowledge-base:​database-migration:​ispirer-toolkit-faq:​pg_with_ssl_2.jpg?​nolink|}}
 +
 +On the "​Advanced"​ window please check "Use SSL Connection"​ option and after that you will be able to select SSL mode. And according to the SSL mode provide a path to the required certificates.
 +
 +Please note:\\
 +If you will use "​**disable**"​ mode, then you will not need to provide additional information about the certificates.\\
 +If you will use "​**allow**",​ "​**prefer**"​ or "​**require**"​ SSL mode, then you will have to provide a paths to Client Certificate and Client Key.\\
 +If you will use "​**verify-ca**"​ or "​**verify-full**"​ SSL mode, then you will have to provide a paths to Client Certificate,​ Client Key and Root Certificates in appropriate options.
 +
 +\\
 +If you have any other questions regarding the usage of our tool, please contact our support team at [[[email protected]]]