Data360 Analyze

 View Only
  • 1.  Unable to add Proxy info to access Azure PostgresSQL via JDBC

    Posted 03-14-2023 10:56

    Hi,

    We are trying to access a PostgresSQL database located in Azure.

    With Data360 local desktop it works with the standard JDBC node.

    With Data360 server it doesn't work because the internet traffic is closed from the server.

    We usually use a proxy server when we want to access an API from Azure or Snowflake. The http node has an option to add a proxy server & port,but the JDBC node lacks this option.

    Is there another way to add the proxy information to access this Azure PostgresSQL via  proxy?

    Thank you



    ------------------------------
    Sébastien
    ------------------------------


  • 2.  RE: Unable to add Proxy info to access Azure PostgresSQL via JDBC

    Posted 03-20-2023 05:46

    Hi,

    We've done something similar recently and we added the settings into DbOptions, something like this:

    useProxy=true
    proxyHost=[proxy server]
    proxyPort=[proxy port]



    ------------------------------
    Annie Kay
    LEXISNEXIS RISK SOLUTIONS
    NEW YORK
    ------------------------------



  • 3.  RE: Unable to add Proxy info to access Azure PostgresSQL via JDBC

    Posted 03-20-2023 07:55

    Thank you Annie. 

    I tried that but it doesn't even seem to use the proxy information entered this way.

    Sebastien



    ------------------------------
    Sébastien Godet
    E.ON Sverige
    MALMOE
    ------------------------------



  • 4.  RE: Unable to add Proxy info to access Azure PostgresSQL via JDBC

    Employee
    Posted 03-21-2023 07:31

    When making a connection to a postgreSQL database Data360 Analyze utilizes the functionality of the postgreSQL JDBC driver to make the required connection.

    The connection to the database uses a TCP connection - it does not utilize HTTP. 

    The postgreSQL JDBC driver properties are described in the driver's documentation. This indicates there is no support for a proxy server in the driver. 

    If a firewall is preventing a direct connection to the target database then you would need to either:

    1) open an egress pinhole in the firewall

    2) Configure the node to make a connection to a suitable proxy server and then configure the proxy server to re-write the TCP destination information to route the connection to the target database.



    ------------------------------
    Adrian Williams
    Precisely Software Inc.
    ------------------------------