Integration with Azure KeyVault
Currently, we store sensitive information in API Portal - Properties and use them as {{key}}
Provide integration of Azure KeyVault so that sensitive information can be stored in Azure KeyVault and allow using it inside API methods or policies like {{vault:key}}
By this feature, we will be able to centralize all the keys in the Azure KeyVault and use Properties only for non-sensitive information.
Puneet Ghanshani
shared this idea
8 comments
-
Gert Vloo
commented
Is there some update on this request?
I would like to link a property to a key-vault, like how it is done in api-apps with the settings. That way the use of properties in policies stays the same and the costs of querying the key-vault are reduced.Example: @Microsoft.KeyVault(SecretUri=https://KEYVAULTNAME.vault.azure.net/secrets/VERYSECREDPASSWORD)
-
Kris Akins
commented
Support for certificates is good, but will there general support for key vault secrets, such as JWT signing keys?
-
Jorge Cruz
commented
Include the ability to retrieve Secrets from key vault and leverage them within Azure APIM Policy
-
Anonymous
commented
include ARM template integration, it's a nightmare now having to do base64 encoding and pass files -- would be better to pass a keyvault URI or resource reference
-
Laurent Lesle
commented
+ key rotation
-
Alec Massey
commented
This is a definite must for Azure - AWS already offer this kind of integration
-
Dan Byrne
commented
We also request to have the API Management Subscription Keys stored in KeyVault for security purposes
-
Erik Oppedijk
commented
And please add a way to connect to different keyvaults, when using multiple tenants (dev/test/prod)