[Cloudera][DriverSupport] (1100) SSL certificate verification failed because the certificate is missing or incorrect. (1100) (SQLDriverConnect); [HY000] [Cloudera][DriverSupport] (1100) SSL certificate verification failed because the certificate is missing or incorrect. (1100)

[#1]

Recently started getting the following error when attempting and odbc connection using 2.06.09.1009 windows 64-bit odbc driver:

"[Cloudera][DriverSupport] (1100) SSL certificate verification failed because the certificate is missing or incorrect. (1100) (SQLDriverConnect); [HY000] [Cloudera][DriverSupport] (1100) SSL certificate verification failed because the certificate is missing or incorrect. (1100)"

Upon further investigation using openssl against the cacerts.pem file we discovered there are several components in the pem file that have expired.

Where can we get an update cacerts.pem file?

Thanks. 

[#2]

Hello @WMichael 

Thank you for reaching out to Cloudera Community

How to update cacerts.pem:

1. 1. Locate the file:

   Find where your cacerts.pem file is stored on your system. The location varies depending on your operating system, web server, or application (e.g., PHP, OpenSSL). 
2. 2. Obtain a new cacerts.pem:

   You can either download a fresh cacerts.pem from a trusted source (like your operating system vendor or a reputable security provider) or copy from the working node or else generate one yourself third party reference.
3. 3. Replace the old file:

   Carefully replace the expired cacerts.pem file with the new one. 
4. 4. Configure your system:

   If necessary, update your system's configuration to point to the new cacerts.pem file. For example, you might need to adjust the curl.cainfo setting in your php.ini file. 
5. 5. Restart services:

   After updating the file and configuration, restart any relevant services (e.g., web server, PHP) to apply the changes. 

[#3]

Thanks. 

The installation of the ODBC driver installation included the cacerts.pem file.  Is there a way to get an updated file (without reinstalling the ODBC Driver)?

[#4 · Accepted solution]

Thanks @WMichael 

I am not sure about any other way but reinstalling the ODBC driver should fix the issue is certs are bundled with the driver only

[#5]

Turns out a change had been made on the Server that required a change in the way the ODBC connection was being made.  After adding "UseSystemTrustStore=1" to our connection string, then out problem was solved.

"