Azure Key Vault helps solve the following problems:
Source code | Package (PyPI) | API reference documentation | Product documentation | Samples
Install the Azure Key Vault Secrets client library for Python with pip:
pip install azure-keyvault-secrets
Python 2.7, 3.5.3, or later
A Key Vault. If you need to create one, you can use the Azure Cloud Shell to create one with these commands (replace "my-resource-group"
and "my-key-vault"
with your own, unique names):
(Optional) if you want a new resource group to hold the Key Vault: .. code-block:: sh
az group create –name my-resource-group –location westus2
Create the Key Vault:
az keyvault create --resource-group my-resource-group --name my-key-vault
Output:
{ "id": "...", "location": "westus2", "name": "my-key-vault", "properties": { "accessPolicies": [...], "createMode": null, "enablePurgeProtection": null, "enableSoftDelete": null, "enabledForDeployment": false, "enabledForDiskEncryption": null, "enabledForTemplateDeployment": null, "networkAcls": null, "provisioningState": "Succeeded", "sku": { "name": "standard" }, "tenantId": "...", "vaultUri": "https://my-key-vault.vault.azure.net/" }, "resourceGroup": "my-resource-group", "type": "Microsoft.KeyVault/vaults" }
The "vaultUri"
property is the vault_url
used by SecretClient
In order to interact with a Key Vault’s secrets, you’ll need an instance of the ``SecretClient` <https://azure.github.io/azure-sdk-for-python/ref/azure.keyvault.secrets.html#azure.keyvault.secrets.SecretClient>`_ class. Creating one requires a vault url and credential. This document demonstrates using DefaultAzureCredential
as the credential, authenticating with a service principal’s client id, secret, and tenant id. Other authentication methods are supported. See the azure-identity documentation for more details.
This Azure Cloud Shell snippet shows how to create a new service principal. Before using it, replace “your-application-name” with a more appropriate name for your service principal.
Create a service principal: .. code-block:: Bash
{ "appId": "generated app id", "displayName": "my-application", "name": "http://my-application", "password": "random password", "tenant": "tenant id" }
Use the output to set AZURE_CLIENT_ID (appId), AZURE_CLIENT_SECRET (password) and AZURE_TENANT_ID (tenant) environment variables. The following example shows a way to do this in Bash:
export AZURE_CLIENT_ID="generated app id" export AZURE_CLIENT_SECRET="random password" export AZURE_TENANT_ID="tenant id"
Authorize the service principal to perform key operations in your Key Vault:
az keyvault set-policy --name my-key-vault --spn $AZURE_CLIENT_ID --key-permissions backup delete get list create
Possible key permissions:
Key management: backup, delete, get, list, purge, recover, restore, create, update, import
Cryptographic operations: decrypt, encrypt, unwrapKey, wrapKey, verify, sign
With a SecretClient
, you can get secrets from the vault, create new secrets and update their values, and delete secrets, as shown in the examples below.
A secret consists of a secret value and its associated metadata and management information. For this library secret values are strings, but Azure Key Vault doesn’t store them as such. For more information about secrets and how Key Vault stores and manages them, see the Key Vault documentation .
This section contains code snippets covering common tasks:
set_secret
creates a secret in the vault. If a secret with the same name already exists, a new version of that secret is created.
secret = secret_client.set_secret("secret-name", "secret-value") print(secret.name) print(secret.value) print(secret.properties.version)
get_secret
retrieves a secret previously stored in the Key Vault.
secret = secret_client.get_secret("secret-name") print(secret.name) print(secret.value)
update_secret
updates a secret’s metadata. It cannot change the secret’s value; use ``set_secret` <#create-a-secret>`_ to set a secret’s value.
# Clients may specify the content type of a secret to assist in interpreting the secret data when it's retrieved content_type = "text/plain" # You can specify additional application-specific metadata in the form of tags. tags = {"foo": "updated tag"} updated_secret_properties = secret_client.update_secret_properties("secret-name", content_type=content_type, tags=tags) print(updated_secret_properties.updated_on) print(updated_secret_properties.content_type) print(updated_secret_properties.tags)
begin_delete_secret
requests Key Vault delete a secret, returning a poller which allows you to wait for the deletion to finish. Waiting is helpful when the vault has soft-delete enabled, and you want to purge (permanently delete) the secret as soon as possible. When soft-delete is disabled, deletion is always permanent.
deleted_secret = secret_client.begin_delete_secret("secret-name").result() print(deleted_secret.name) print(deleted_secret.properties.deleted_date)
This example lists all the secrets in the vault. The list doesn’t include secret values; use ``get_secret` <#retrieve-a-secret>`_ to get a secret’s value.
secret_properties = secret_client.list_properties_of_secrets() for secret_property in secret_properties: # the list doesn't include values or versions of the secrets print(secret_property.name)
This example creates a secret in the Key Vault with the specified optional arguments.
from azure.identity.aio import DefaultAzureCredential from azure.keyvault.secrets.aio import SecretClient credential = DefaultAzureCredential() secret_client = SecretClient(vault_url="https://my-key-vault.vault.azure.net/", credential=credential) secret = await secret_client.set_secret("secret-name", "secret-value") print(secret.name) print(secret.value) print(secret.properties.version)
This example lists properties of all the secrets in the specified Key Vault. Note that secret values are not included.
secret_properties = secret_client.list_properties_of_secrets() async for secret_property in secret_properties: # the list doesn't include values or versions of the secrets print(secret_property.name)
Key Vault clients raise exceptions defined in ``azure-core` <https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/core/azure-core/docs/exceptions.md>`_. For example, if you try to get a key that doesn’t exist in the vault, SecretClient
raises ResourceNotFoundError
:
from azure.core.exceptions import ResourceNotFoundError secret_client.begin_delete_secret("my-secret").wait() try: secret_client.get_secret("my-secret") except ResourceNotFoundError as e: print(e.message)
Network trace logging is disabled by default for this library. When enabled, HTTP requests will be logged at DEBUG level using the logging
library. You can configure logging to print debugging information to stdout or write it to a file:
from azure.identity import DefaultAzureCredential from azure.keyvault.secrets import SecretClient import sys import logging # Create a logger for the 'azure' SDK logger = logging.getLogger('azure') logger.setLevel(logging.DEBUG) # Configure a console output handler = logging.StreamHandler(stream=sys.stdout) logger.addHandler(handler) credential = DefaultAzureCredential() # Enable network trace logging. Each HTTP request will be logged at DEBUG level. client = SecretClient(vault_url="https://my-key-vault.vault.azure.net/", credential=credential, logging_enable=True)
Network trace logging can also be enabled for any single operation:
secret = secret_client.get_secret("secret-name", logging_enable=True)
Several samples are available in the Azure SDK for Python GitHub repository. These provide example code for additional Key Vault scenarios:
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Developer Documentation
ncG1vNJzZmiZqqq%2Fpr%2FDpJuom6Njr627wWeaqKqVY8SqusOorqxmnprBcHDWnploqKmptbC6jpqxrqqVYrimxdWarKWsXaiypL7ErapobF5le3GulGigp5yVrXupwMyl