Configuring SSL Verification

Note:

In this documentation, "SSL" indicates both TLS (Transport Layer Security) and SSL (Secure Sockets Layer). The connector supports industry-standard versions of TLS/SSL.

When connecting to data stores, by default the Simba HubSpot JDBC Connector uses SSL encryption. The connector also uses peer verification to verify the identity of the server, and host verification to make sure that the host name in the server certificate matches the host name of the server that you are connecting to.

Note:

For peer verification, if the server certificate is not issued by a certificate authority (CA), then add the server certificate to your Java KeyStore.

You can disable peer verification so that the connector does not verify the identity of the server, and disable host verification so that the connector accepts all host names.

Configuring Host and Peer Verification

To disable host or peer verification:

To disable host verification so that the connector accepts all host names, set the UseHostVerification property to 0.
To disable peer verification so that the connector does not verify the identity of the server, set the UsePeerVerification property to 0.

For example, host and peer verification are both disabled in the following connection URL:

jdbc:hubspot://localhost;Host=https://api.hubapi.com;Auth_Type=Access Token;Auth_AccessToken=f357a49a-c75c-417c-b002-2f81242df409;UseHostVerification=0;UsePeerVerification=0;

jdbc:hubspot://;Host=wd2-services1.workday.com;Auth_type=OAuth 2.0;Auth_Client_Id=a1b2c3;Auth_Client_Secret=abcfe;Tenant_Id=abcefg;Auth_BaseRedirectUri=https://localhost:6367;TrustCertsPath=C:\\Users\\john\\keystore.jks;TrustCertsPwd=123456;UseHostVerification=0;UsePeerVerification=0

jdbc:hubspot://;Host=wd2-services1.workday.com;Auth_type=OAuth 2.0;Auth_Client_Id=a1b2c3;Auth_Client_Secret=abcfe;Tenant_Id=abcefg;UseEncryptedEndpoints=0;