Hybrid Data Pipeline must be registered as a client application with the data store or data service you are accessing before it can be integrated into an OAuth 2.0 grant flow. The following steps show the general workflow that may be required to register Hybrid Data Pipeline as a client application.

  1. To begin the registration process, you will need to sign in to the data store or service you plan to access with Hybrid Data Pipeline. For example, you would need to sign in to the Azure portal to register Hybrid Data Pipeline for connectivity to Dynamics 365 apps. Similarly, you would need to sign in to Google to register Hybrid Data Pipeline as a client application with Google Analytics or Google BigQuery.
  2. From the data store's user interface, you will need to specify the fully qualified domain name of your Hybrid Data Pipeline instance. For example, https://hdp-example:8443/hdpui.
  3. From the data store's user interface, you will need to specify a redirect or callback URI. The redirect URI takes the form https://hdp-fqdn/hdpui/oauth2callback where hdp-fqdn is the fully qualified domain name of your Hybrid Data Pipeline instance.
    Note: The redirect URI is also available as the OAuth Redirect URI through the Hybrid Data Pipeline Web UI when creating a data source.
  4. During the registration process, you may have to select scopes to limit application access to the data store. Record any scopes you select, or any required scopes. These scopes will need to be specified as a space-separated list for the Scopes parameter when you create a Hybrid Data Pipeline data source.
  5. Record the following OAuth information during the registration process. Depending on the OAuth grant flow you are using, some or all of this information may be required to create a Hybrid Data Pipeline data source.
    • Authorization URI
    • Token URI
    • Client ID
    • Client Secret
    • Scope

Additional guidance for registering client applications with data stores or data services is provided in Progress DataDirect connector documentation. See the following resources for details.

Note: Not all the steps in these resources may apply when registering Hybrid Data Pipeline as a client application.