Denodo

Before connecting to a U-M API Directory API, you need to have:
Tableau uses a built-in connector to connect to Denodo views. After launching Tableau, complete the steps below to configure your connection.
SQL clients can be used to connect to Denodo, however they must be configured before use. First, the Denodo JDBC driver needs to be downloaded to the client workstation. Then, the SQL client connection needs to be configured to use the driver. Each SQL client handles this differently.  DBeaver is the U-M recommended SQL client for use with Denodo. Follow the instructions below to configure DBeaver using Kerberos authentication with supplied userid/password (not SSO). 
This document describes the process to create a Denodo data source against a Dropbox file via the Dropbox API.  Note that Dropbox shareable links do not work with Denodo due to a failure to follow Dropbox redirects.  Authenticated calls via the API are required to connect Denodo to any Dropbox files.  Dropbox API utilities are used to generate an OAuth token that can be stored in Denodo.
This document describes the process to create a Denodo data source against Google BigQuery using the OAuth client ID pre-generated token scheme. This document assumes use of the JDBC Simba BigQuery driver. Data Owner Configures the GCP Project Within the GCP project:
This document describes the process to create a Denodo data source against Google BigQuery using the OAuth client ID pre-generated token scheme. In general, the data source is configured using a Google service account, but there are instances where an OAuth client ID approach is necessary. Note: The Desktop App Configuration is recommended by U-M. Use that model, if possible.
This document contains information related to creating a Denodo data source against a Google Sheet using the Denodo Google Sheets Custom Wrapper.
This document describes how to create a Denodo data source against a One Drive file using either an Authenticated or Unauthenticated method.  Authenticated Method If the file is not shared, shared privately with specific users, or shared via a link with users in the U-M organization, authenticated calls via the Microsoft Graph API are required. Azure API utilities is used to generate an OAuth token that can be stored in Denodo.
Denodo developers need to install the Virtual DataPort client and have their account configured before working in Denodo. Follow the applicable steps below to download, install, and configure the software.  Note that you will need to be on the VPN to connect to the ITS Denodo instance.
Access to the Denodo system and views created within Denodo are controlled through MCommunity groups. Virtual Database (VDB) owners manage users’ privileges by adding/removing individuals from these groups.  When requesting a new VDB, the online request form requires an MCommunity administrative group name be provided. This group will own the groups with access to the VDB. It will also be notified when changes to U-M Data Warehouse views may impact the VDB environment, therefore it must be configured to receive email from non-members.