The AuthHeaders won't stay in REST API linked service

Question

In a linked service used to connect to Airtable, I can input the Auth Headers, publish the change, and execute properly a pipeline on the fly. At that moment, I can also see in the underlying JSON the portion relating to the header.

"authHeaders": {
                "Authorization": {
                    "type": "AzureKeyVaultSecret",
                    "store": {
                        "referenceName": "LS_KV_DWHSYNAPSE",
                        "type": "LinkedServiceReference"
                    },
                    "secretName": "airtable-token"
                }
            }

However, as soon as I CTRL+F5 (full page refresh), when I open back the interface or the underlying JSON code, the authHeaders disappear.

It is not clear at what moment it disappears, but my problem is that is never stays because at night when our data pipelines execute, they hit an error related to authentication for the Airtable API call..

Our consultant was able to reproduce the problem in another synapse workspace.

Steps to reproduce:

1. In a REST API linked service (LS), set any auth header
   1. Any name, and a value refering to KeyVault. (not necessary though)
2. Save and publish
3. CTRL+F5 for full refresh
4. Reopen the LS or check the JSON
5. The headers have disappeared

Answer 1

Hi @phemanth , thanks for the reply

1. Azure Synapse Analytics
2. I am not familiar with Azure Synapse logs. I did not know what to look for. Tables, queries, functions, and history were all empty
3. We updated another linked service around the same time. We had to update our postgresql connector to the "version2" as specified in an important note of this article: https://learn.microsoft.com/en-us/azure/data-factory/connector-postgresql?tabs=data-factory

Answer 2

@Vincent Labrecque

To check the Azure Synapse logs, follow these steps:

1. Go to your Azure Synapse workspace.
2. Click on the "Monitor" tab on the left-hand side menu.
3. Click on "Pipeline runs" or "Activity runs" depending on what you're looking for.
4. Filter the results by the time range when the AuthHeaders disappeared.
5. Look for any errors or warnings related to the linked service or pipeline.

If you're not familiar with the logs, you can also try checking the "Diagnostic settings" in your Azure Synapse workspace. This will allow you to configure logging and monitoring for your workspace.

1. Check the linked service configuration: Double-check the linked service configuration to ensure that the AuthHeaders are correctly set up and not being overridden by any other settings.
2. Test with a different authentication method: Try using a different authentication method, such as a static value instead of a KeyVault reference, to see if the issue persists.
3. Check the PostgreSQL connector update: Since you updated the PostgreSQL connector to version 2, try rolling back to the previous version to see if the issue is related to the update.