Question
· Apr 13

Cache 2017 Linux ODBC with SSL Configuration

Using Cache 2017.2 sever as my target.

I have a x64 Ubuntu client setup going.  This is NOT server. Just client. 

I have the Linux Ubuntu x64 ODBC driver gzip file. 

ODBC-2018.1.5.659.0-lnxubuntux64.tar.gz is all I could find.  Someone posted it in another post.

I can connect to a test sever that does NOT use SSL.  That works pretty easily.

But I have A server with SSL enabled. With Windows Cache ODBC drivers I can use SSL just fine.

This is what my SSLDefs.ini file on the Windows machines look like and it works just fine.

YES. I know. Not super secure because of the settings. Man in the middle, ect,ect ... but that is how it is currently working.
So I have to work with it.  ( Not my server )

[MyServer1 TLS to an instance without TLS-protected InterSystems ODBC]
Address=192.168.50.130
Port=1972
SSLConfig=TestServerSSL

[TestServerSSL]
Protocols=24
KeyType=2
VerifyPeer=0
CipherList=ALL:!aNULL:!eNULL:!EXP:!SSLv2
Password=
CertFile=
KeyFile=
CAfile=
[TLSNoVerify]
Protocols=16
KeyType=2
VerifyPeer=0
CipherList=ALL:!aNULL:!eNULL:!EXP:!SSLv2
Password=
CertFile=
KeyFile=
CAfile=

I can't find any good info for the Linux setup.
Exactly how to setup odbc.ini
How to possibly setup the equivalent of SSLdefs.ini for linux.
What exact path variables and such is needed.
ISC_SSLconfigurations path.
LD_LIBRARY_PATH for cconnect?
possibly a 3rd or 4th ini setting maybe?

Grok and ChatGPT can't make heads or tails of any of this. 
As I think it confuses IRIS and Cache so you end up with wonky results.

I just need example files for each exact INI file.
Where they go maybe?
and what system path variables and such to set to exactly.

 

Example of ODBC for Windows driver working fine with the SSL settings.

 

This is what I see when trying to connect to the SSL enabled server.

stevenc@HP:/etc$ isql -v TestServer
[S1000][unixODBC][Cache ODBC][State : S1000][Native Code 65530]
[libcacheodbc.so]
UNKNOWN MSG
[ISQL]ERROR: Could not SQLConnect
Product version: Caché 2017.1
Discussion (1)1
Log in or sign up to continue