Unable to use JDBC driver with proxyHost with dashes

Whenever I try to initialize JDBC driver with proxy settings as part of the Connection String, I am getting an error:

No suitable driver found for jdbc:snowflake://myaccount.snowflakecomputing.com:443?CLIENT_SESSION_KEEP_ALIVE=true&db=TEST_DB&proxyHost=some-host-with-dashes.com&proxyPort=1234&schema=PUBLIC&useProxy=true&warehouse=TEST_WH

When proxyHost doesn’t include dashes or any other special characters, the driver initializes but fails on network error. An example proxyHost that doesn’t fail: jdbc:snowflake://myaccount.snowflakecomputing.com:443?CLIENT_SESSION_KEEP_ALIVE=true&db=TEST_DB&proxyHost=localhost&proxyPort=1234&schema=PUBLIC&useProxy=true&warehouse=TEST_WH.

Any idea what’s going on?

[smtakeda]

We are working on the fix.

On Mon, Jun 24, 2019 at 6:15 AM Moty Michaely [e-mail] wrote:

@smtakeda https://github.com/smtakeda Hey, any updates on this? Thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/snowflakedb/snowflake-jdbc/issues/135?email_source=notifications&email_token=AABJMZKWZMYOWBTQN37BIXDP4DCFZA5CNFSM4HYYN3W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYM4FNA#issuecomment-505004724, or mute the thread https://github.com/notifications/unsubscribe-auth/AABJMZNFPMQCUC6KAML7QITP4DCFZANCNFSM4HYYN3WQ .

– Shige Takeda [e-mail]

[motymichaely]

@smtakeda and @mknister Thanks for your comments!

Specifying a Proxy Server by Setting JVM Options won’t work for us as we are running several workloads under the same JVM process, and setting the proxy on JVM level will route all traffic through the proxy. We only need the Snowflake connection go through the proxy.

Our use case is whitelisting a single IP in our Snowflake Security policy by having the connection go through a proxy. We tried sorting this out using an SSH tunnel but this doesn’t work due to certificate mismatch.

Currently we are working this around by having a dedicated NAT gateway to have single IP but we’d like to avoid having a dedicated NAT gateway for this purpose. I hope this makes sense.

@smtakeda - Any ETA for a fix?

Thanks a bunch!