Refer to Azure Key Vault secrets in dynamic content
If I need to crawl a restful API which is protected with an API key, the only way to set that key is by injecting an additional header on the dataset level. This key is stored in clear text, which is poor security.
To make matters worse, if git integration is enabled, that key is even committed into version control.
There should be a way to fetch values from Azure Key Vault elsewhere than just for setting up linked services. Alternatively, the REST linked service should support authentication with an API key.
Veli-Jussi Raitila
shared this idea
2 comments
-
Henko Kors
commented
Yes, we deff need a way to refer to a secret within the linked key vault. Instead of pulling a secret with the web activity and parameterize that content.
-
Eric
commented
This would be especially nice for providing a secret value in a pipeline activity. It seems the only way to do this is via a web activity (documented here: https://docs.microsoft.com/en-us/azure/data-factory/how-to-use-azure-key-vault-secrets-pipeline-activities).
This feels extremely clunky if you've already defined a Key Vault linked service. It would be great to just reference the Key Vault dynamically with a syntax like: @linkedService('key_vault_name').mySecret