OAS -DV-Snowflake JDBC connection- Parameter To Support Key Value Pairs — Oracle Analytics

Oracle Analytics Cloud and Server Idea Lab

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

OAS -DV-Snowflake JDBC connection- Parameter To Support Key Value Pairs

129
Views
3
Comments
VaishnaviD-Oracle
VaishnaviD-Oracle Rank 1 - Community Starter

It would be helpful if we have a textbox as part of the connection definition screen that accepts free text to support key value pairs for correct driver/additional configurations.

Note: This is already available as part of the weblogic snowflake-Datasource definitions.

Current connection string Vs Expected connection string to establish connection from OAS DV to snowflake as follows:

Current connection string being used -  jdbc:snowflake://XXXX.snowflakecomputing.com/?useProxy=true&proxyHost=XXXX&proxyPort=XXXX&db=XXXXX

Expected connection string- jdbc:snowflake://XXXX.snowflakecomputing.com/?useProxy=true&proxyHost=XXXX&proxyPort=XXXX&client_session_keep_alive=true&jdbc_query_result_format=json&db=XXXXX

================================

Weblogic snowflake datasource parameter declaration:

proxyHost=XXXX

useProxy=true

jdbc_query_result_format=json

client_session_keep_alive=true

database=XXXXX

proxyPort=8000

user=XXXXX

4
4 votes

Submitted · Last Updated

Comments

  • User_SK2UI
    User_SK2UI Rank 3 - Community Apprentice

    Recently our security teams are insisting that we need to use Key Value Pair authentication to connect to snowflake from OAC . Did Oracle make any progress of including parameters for Key-Value pair while configuring snowflake connection in OAC DV or in OAC RPD ?

  • User_3KBUW
    User_3KBUW Rank 1 - Community Starter

    Has there been any developments/comments on this issue. Apparently Snowflake are deprecating all username password authentication from November 25!

  • Ciaran
    Ciaran Rank 4 - Community Specialist

    I completely agree.

    I feel Oracle is behind the times on this one and is loosing more competitive advantages compared to other BI tools.

    I also posted a similar message some time ago but took a more generic approach to the change for all data source definitions. (See below)

    Why would Oracle restrict what can be done here.. let free the data source driver parameters and stop restricting… you cannot cater for all scenarios and changes. It's easier for Oracle and the customer gets what they want.