question

SudhirKoka-4687 avatar image
0 Votes"
SudhirKoka-4687 asked SudhirKoka-4687 answered

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

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-data-factoryazure-synapse-analyticspartner-center-api
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @SudhirKoka-4687,
Thanks for the question and using MS Q&A platform.

We were able to confirm that the Azure Synapse is sending a Resource form field with a blank value when no resource is configured.

From the screenshot its clear that the resource header is blank . if you do not send any value in the header it will not reach the API . I am sorry as I am sure I ammissing something here . Can you please help and elaborate the issues ?

We will wait to hear from you . .
Thanks
Himanshu


0 Votes 0 ·

1 Answer

SudhirKoka-4687 avatar image
0 Votes"
SudhirKoka-4687 answered

@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

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.