REST connector in Azure Synapse sends the resource header even when resource field is empty

Sudhir Koka 1 Reputation point
2022-04-26T20:45:41.657+00:00

I am trying to configure the REST connector in Microsoft Azure Synapse service to extract data from Aveva DataHub using OAuth credentials to analyze it with Azure Synapse and it fails with the invalid_target error uploaded as attachment.

We were able to confirm that the Azure Synapse is sending a Resource form field with a blank value when no resource is configured. This is an issue because our token endpoint is implemented by Duende IdentityServer and it rejects token requests that contain a resource with no value in the form fields (if the resource field is present at all, a valid absolute URI is required). The Aveva DataHub does not use the resource field at all. Please let us know if there is way to configure the REST connector to stop sending an empty Resource form field when no resource is specified in the OAuth connection settings. I have attached a screenshot from beeceptor showing that Azure Synapse connector sends a blank resource header. 196732-restapierrormsg.png196723-restconnectorsettings.png196706-resourceheaderwithblankvalue.png

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
4,396 questions
Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,603 questions
Microsoft Partner Center API
Microsoft Partner Center API
Microsoft Partner Center: A Microsoft website for partners that provides access to product support, a partner community, and other partner services.API: A software intermediary that allows two applications to interact with each other.
316 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sudhir Koka 1 Reputation point
    2022-04-27T22:18:06.14+00:00

    @HimanshuSinha-msft ,

    The Aveva DataHub is using the Duende IdentityServer4 open source software to handle all the OAuth token endpoint calls. It rejects the token requests that contain a resource header with a blank value from Azure Synapse. If the resource field is present at all, a valid absolute URI is required. According to our Identity team, this is working per OAuth specifications.

    Aveva DataHub does not use any resource fields. Hence, Azure Synapse should not be sending the resource header when there is no resource field provided. Is there a way to configure the REST connector such that the resource header is not sent in the token request?

    Thanks,
    Sudhir

    0 comments