Share via

ADF REST Linked Services Auth Headers are not working

Joseph Lee 50 Reputation points
Sep 4, 2024, 11:48 PM

This stackoverflow thread has a good explanation of the same issue I am seeing: https://stackoverflow.com/questions/78948962/adf-rest-linkedservice-is-missing-authheader-in-live-mode-after-publishing/78950885#78950885

I need auth headers to be entered and using Azure Key Vault, but that doesn't appear to be working all of a sudden.

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
11,397 questions
{count} votes

Accepted answer
  1. Bhargava-MSFT 31,236 Reputation points Microsoft Employee
    Sep 6, 2024, 3:18 PM

    Hello Joseph Lee and Chris Meesters,

    The product team has deployed the fix. Please validate and let me know if you are still facing the same issue.

    1 person found this answer helpful.

3 additional answers

Sort by: Most helpful
  1. Chris Meesters 85 Reputation points
    Sep 5, 2024, 9:14 AM

    Seems that Microsoft has stated that this is due to a bug in a different post:

    https://learn.microsoft.com/en-us/answers/questions/2036344/auzure-synapse-rest-linked-service-doesnt-save-aut

    Stating that: "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."

    Which is completely useless as far as workarounds go... Eager for MS to fix this issue.

    1 person found this answer helpful.
    0 comments No comments

  2. Chris Meesters 85 Reputation points
    Sep 6, 2024, 9:59 AM

    Hello again,

    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 the Auth headers coming through when publishing/deploying. 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!

    0 comments No comments

  3. Swati B 0 Reputation points
    Oct 8, 2024, 3:35 PM

    I am still seeing the issue where auth header parameters are not getting moved to higher environments. Our higher environments are not connected to any Git repository, we are moving arm template files only. Can someone please advise how we can fix the issue.

    0 comments No 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.