Can Qlik replicate work with encrypted turn on for MySQL as endpoint?

desmondchew — Fri, 31 May 2024 05:23:22 GMT

I have enabled "require_secure_transport=ON" in MySQL endpoint. The task started to fail and the error message is:

(Connections using insecure transport are prohibited while --require_secure_transport=ON.)

Is there a workaround to bypass or fix this?

Thank you.

Desmond

Re: Can Qlik replicate work with encrypted turn on for MySQL as endpoint?

john_wang — Fri, 31 May 2024 05:50:06 GMT

Hello @desmondchew ,

Thanks for reaching out to Qlik Community!

This is a pure MySQL Client/Server communication settings issue. With require_secure_transport enabled, client connections to the server are required to use some form of secure transport, and the server permits only TCP/IP connections that use SSL, The server rejects nonsecure connection attempts, that's why you got the error.

To establish encrypted connections, the certificate and key files are required:

ssl_ca: The path name of the Certificate Authority (CA) certificate file. (ssl_capath is similar but specifies the path name of a directory of CA certificate files.)
ssl_cert: The path name of the server public key certificate file. This certificate can be sent to the client and authenticated against the CA certificate that it has.
ssl_key: The path name of the server private key file.

These files should be provided in Qlik Replicate Endpoint, a sample:

We strongly suggest you new a 64-bit ODBC DSN and use it to test the connectivity, if the DSN works, then we may 'copy' the same settings to Qlik Replicate Endpoint.

Hope this helps.

John.

topic Re: Can Qlik replicate work with encrypted turn on for MySQL as endpoint? in Qlik Replicate

Can Qlik replicate work with encrypted turn on for MySQL as endpoint?

Re: Can Qlik replicate work with encrypted turn on for MySQL as endpoint?