MySQL DAM and $sslset()
reg.paling at lokanet.com
Sat May 1 06:57:38 UTC 2021
I am trying to connect from my Omnis dev kit to a MySQL database on a
remote server. (It is a WordPress database).
I can connect to another non-WordPress MySQL database on a totally
different remote site, so I know the DAM and network etc is working.
I can connect OK from MySQLWorkbench.app on my Mac, using a "Standard
(TCP/IP)" connection with just a username and password that were
supplied to me.
In MySQLWorkbench, executing "SHOW STATUS LIKE 'Ssl_cipher';" gives
... which I take as an indication that MySQLWorkbench appears to have
bumped up the connection to a secure connection even though I did not
ask for that. Would that be correct?
When I try to connect from Omnis, I get error 2026 "SSL connection
error: unknown error number"
I am guessing I have to supply some certificate files to support an SLL
connection from Omnis. From what I have read, if I supply just a key
and certificate to support encryption from my end, I don't need to
install any certificate from the server. The fact that I can connect
from MySQLWorkbench proves I don't need any certificate from the server.
I gather I can use $sslset() to tell the DAM which certifcate file/s to
use, but I don't know what the parameters mean:
From the Omnis documentation:
SessObj.$sslset([cKey, cCert, cCA, cCAPath, cCipher]) is used for
establishing a secure connection using SSL. It must be called before
$logon(). cKey is the path name to the key file. cCert is the path name
to the certificate file. cCa is the path name to the certificate
authority file. cCAPath is the path name to a directory that contains
trusted SSL CA certificates in pem format. cCipher is a list of
permissible ciphers to use for SSL encryption. Any unused SSL parameters
will be treated as NULL.
Can anyone please point me in the right direction?
More information about the omnisdev-en