Auzure Synapse - REST Linked Service doesn't save Auth headers parameters after publish

Ilya Kutsenko 35 Reputation points
2024-09-04T07:30:25.59+00:00

Hello, I have a Synapse workspace and last Monday I have discovered this bug:

1.Synapse is in Synapse Live modeUser's image

2.Open Manage - Linked Services - New - select REST

3.Fill all required fields and select Authorization type "Anonymous" as shown below and add some Auth Header:

User's image

4.Press save below, then "Publish all"

User's image

5.Wait till successful publish

User's image

6.Then refresh the browser page and reopen newly created REST linked service, as you can see below all auth headers are gone

User's image

I've tested workspace deployment from ci/cd and it looks the same. For HTTP and AzFun connectors headers are saved correctly, the only issue is REST.

Is it known issue and how long will it take to fix it?

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,858 questions
Accepted answer
  1. Chris Meesters 85 Reputation points
    2024-09-06T09:57:59.9466667+00:00

    Hi Ilya,

    We seem to have figured out a workaround. For some reason, the authorizationHeader value gets put into an encrypted variable upon deployment due to a 'security improvement' that was implemented by Microsoft. However, this only happens when a single auth header value is present. Adding another auth header with a nonsense value allows you to successfully deploy the Rest LS with auth headers intact.

    E.g.:

    User's image

    Leads to...

    User's image

    No headers.

    But this:

    User's image

    Leads to retained headers!

    Still eager for Microsoft to fix this issue, so we don't have to insert nonsense values in our auth headers as a workaround.

    Hope this works for your situation as well!

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Bhargava-MSFT 30,816 Reputation points Microsoft Employee
    2024-09-04T12:29:09.13+00:00

    Hello Ilya Kutsenko,

    Welcome to the Microsoft Q&A forum.

    From your screenshot, it appears that you have added the value from Azure Key Vault (AKV).

    If this is correct:

    The issue is due to a bug, and the product group is working on a fix. However, there is no ETA at this time.

    Workaround: You need to remove the AKV until the permanent fix is deployed.

    I hope this answers your question. Please let me know if you have any further questions.

    2 people found this answer helpful.
    0 comments
  2. Ilya Kutsenko 35 Reputation points
    2024-09-09T06:25:19.0533333+00:00

    Good day,

    I can confirm that original issue was fixed last Friday, no workaround required anymore.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.