search

SAP / go-hdb

SAP HANA Database Client for Go
Apache License 2.0
168 stars 57 forks source link

Does go-hdb support IP as the 'endpoint' of hana cloud connection? #132

Closed Dan-Jia closed 8 months ago

Dan-Jia commented 9 months ago

Hi, we are trying to test a feature and see if long-running hana connections work fine with the new feature. But in the dev landscape, we can only use the internal-ip of the service as the endpoint of the connection, the hdbsql command we use is for example: hdbsql -n 10.250.0.123:443 -e -u DBADMIN -p Abcde1234 -ssltrustcert -Z disableCloudRedirect=1 -sslsniname 1b2625b0-5a00-4a7c-b4dc-d90f19925678.hana.i123456-haas-hc-dev.dev-aws.hanacloud.ondemand.com

And now we hope to establish more than 50 those long-running connections by using hdb go client to achieve this. We modified the dsn to: hdb://<USER>:<PASSWORD>@10.250.0.123:443?TLSServerName=1b2625b0-5a00-4a7c-b4dc-d90f19925678.hana.i123456-haas-hc-dev.dev-aws.hanacloud.ondemand.com

But then got the following error message: Error: First Ping unsuccesful to 1b2625b0-5a00-4a7c-b4dc-d90f19925d3a.hana.i123456-haas-hc-dev.dev-aws.hanacloud.ondemand.com with error -10709: Connection failed (RTE:[300015] SSL certificate validation failed: host name '10.250.0.123' does not match names in certificate: 'hanacloud.ondemand.com'

So we would like to know, if the go-hdb client support IP as the 'endpoint' of hana cloud connection? If yes, could you let us know, how can we achieve that?

Thanks!

stfnmllr commented 9 months ago

Hi,

hdbsql -n 10.250.0.123:443 -e -u DBADMIN -p Abcde1234 -ssltrustcert -Z disableCloudRedirect=1 -sslsniname 1b2625b0-5a00-4a7c-b4dc-d90f19925678.hana.i123456-haas-hc-dev.dev-aws.hanacloud.ondemand.com

does include -ssltrustcert, for which you might use TLSInsecureSkipVerify as part of the go-hdb DSN.

In regards of 'TLSInsecureSkipVerify' you might double check on https://pkg.go.dev/github.com/SAP/go-hdb/driver as well.

Please let us know if this would solve the issue - thanks!

Dan-Jia commented 9 months ago

Thanks for your quick answer, Stefan! :)

Actually I tried TLSInsecureSkipVerify in the dsn:
hdb://DBADMIN:Abcde1234@10.250.0.123:443?TLSServerName=1b2625b0-5a00-4a7c-b4dc-d90f19925d3a.hana.i123456-haas-hc-dev.dev-aws.hanacloud.ondemand.com?TLSInsecureSkipVerify=true And still see the same error message...

Did I miss anything else?

stfnmllr commented 8 months ago

Closing the ticket as the actual issue isn't go-hdb related.