@azure/keyvault-keys v4.7.2

Azure Key Vault Keys client library for JS

Azure Key Vault is a service that allows you to encrypt authentication keys, storage account keys, data encryption keys, .pfx files, and passwords by using keys that are protected by hardware security modules (HSMs). If you would like to know more about Azure Key Vault, you may want to review What is Azure Key Vault?.

Azure Key Vault Key management allows you to create and control encryption keys that encrypt your data.

Use the client library for Azure Key Vault Keys in your Node.js application to

• Create keys (EC, EC-HSM, RSA, RSA-HSM).
• Import keys.
• Delete keys.
• Update keys.
• Get one or more keys.
• Get one or more deleted keys.
• Recover a deleted key.
• Restore a backed up key.
• Get the versions of a key.
• As well as obtaining the attributes of a key.

Using the cryptography client available in this library you also have access to

• Encrypting
• Decrypting
• Signing
• Verifying
• Wrapping keys
• Unwrapping keys

Please Note: This is a preview version of the Key Vault Keys library

Source code | Package (npm) | API Reference Documentation | Product documentation | Samples

Getting started

Install the package

Install the Azure Key Vault Keys client library using npm

npm install @azure/keyvault-keys

Prerequisites: You must have an Azure subscription and a Key Vault resource to use this package. If you are using this package in a Node.js application, then use Node.js 6.x or higher.

Configure Typescript

TypeScript users need to have Node type definitions installed:

npm install @types/node

You also need to enable compilerOptions.allowSyntheticDefaultImports in your tsconfig.json. Note that if you have enabled compilerOptions.esModuleInterop, allowSyntheticDefaultImports is enabled by default. See TypeScript's compiler options handbook for more information.

Configuring your Key Vault

Use the Azure Cloud Shell snippet below to create/get client secret credentials.

• Create a service principal and configure its access to Azure resources:

  az ad sp create-for-rbac -n <your-application-name> --skip-assignment

  Output:

  {
    "appId": "generated-app-ID",
    "displayName": "dummy-app-name",
    "name": "http://dummy-app-name",
    "password": "random-password",
    "tenant": "tenant-ID"
  }

• Use the above returned credentials information 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"

• Grant the above mentioned application authorization to perform secret operations on the keyvault:

  az keyvault set-policy --name <your-key-vault-name> --spn $AZURE_CLIENT_ID --secret-permissions backup delete get list create

  --secret-permissions: Accepted values: backup, delete, get, list, purge, recover, restore, create

• Use the above mentioned Key Vault name to retrieve details of your Vault which also contains your Key Vault URL:

  az keyvault show --name <your-key-vault-name>

Key concepts

• The Keys client is the primary interface to interact with the API methods related to keys in the Azure Key Vault API from a JavaScript application. Once initialized, it provides a basic set of methods that can be used to create, read, update and delete keys.
• A Key version is a version of a key in the Key Vault. Each time a user assigns a value to a unique key name, a new version of that key is created. Retrieving a key by a name will always return the latest value assigned, unless a specific version is provided to the query.
• Soft delete allows Key Vaults to support deletion and purging as two separate steps, so deleted keys are not immediately lost. This only happens if the Key Vault has soft-delete enabled.
• A Key backup can be generated from any created key. These backups come as binary data, and can only be used to regenerate a previously deleted key.
• The Cryptography client is a separate interface that interacts with the keys API methods in the Key Vault API, ## Authenticating the client. This client focuses only in the cryptography operations that can be executed using a key that has been already created in the Key Vault. More about this client in the Cryptography section.

To use the key vault from TypeScript/JavaScript, you need to first authenticate with the key vault service. To authenticate, first we import the identity and KeysClient, which will connect to the key vault.

import { DefaultAzureCredential } from "@azure/identity";
import { KeysClient } from "@azure/keyvault-keys";

Once these are imported, we can next connect to the key vault service. To do this, we'll need to copy some settings from the key vault we are connecting to into our environment variables. Once they are in our environment, we can access them with the following code:

// DefaultAzureCredential expects the following three environment variables:
// * AZURE_TENANT_ID: The tenant ID in Azure Active Directory
// * AZURE_CLIENT_ID: The application (client) ID registered in the AAD tenant
// * AZURE_CLIENT_SECRET: The client secret for the registered application
const credential = new DefaultAzureCredential();

// Build the URL to reach your key vault
const vaultName = "<YOUR KEYVAULT NAME>";
const url = `https://${vaultName}.vault.azure.net`;

// Lastly, create our keys client and connect to the service
const client = new KeysClient(url, credential);

Examples

The following sections provide code snippets that cover some of the common tasks using Azure Key Vault Keys. The scenarios that are covered here consist of:

• Creating a key.
• Getting a key.
• Creating and updating keys with attributes.
• Deleting a key.
• Iterating lists of keys.

Creating a key

createKey creates a Key to be stored in the Azure Key Vault. If a key with the same name already exists, then a new version of the key is created.

const keyName = "MyKeyName";

const result = await client.createKey(keyName, "RSA");
console.log("result: ", result);

The second parameter sent to createKey is the type of the key. Keys can either be of type: EC, EC-HSM, RSA or RSA-HSM.

Getting a key

The simplest way to read keys back from the vault is to get a key by name. This will retrieve the most recent version of the key. You can optionally get a different version of the key if you specify it as part of the optional parameters.

getKey retrieves a key previous stores in the Key Vault.

const latestKey = await client.getKey(keyName);
console.log(`Latest version of the key ${keyName}: `, getResult);
const specificKey = await client.getKey(keyName, { version: latestKey.version! });
console.log(`The key ${keyName} at the version ${latestKey.version!}: `, getResult);

Creating and updating keys with attributes

The following attributes can also be assigned to any key in a Key Vault:

• tags: Any set of key-values that can be used to search and filter keys.
• keyOps: An array of the operations that this key will be able to perform (encrypt, decrypt, sign, verify, wrapKey, unwrapKey).
• enabled: A boolean value that determines whether the key value can be read or not.
• notBefore: A given date after which the key value can be retrieved.
• expires: A given date after which the key value cannot be retrieved.

An object with these attributes can be sent as the third parameter of createKey, right after the key's name and value, as follows:

const result = await client.createKey(keyName, "RSA", {
  enabled: false
});

This will create a new version of the same key, which will have the latest provided attributes.

Attributes can also be updated to an existing key version with updateKey, as follows:

const result = client.createKey(keyName, "RSA");
await client.updateKey(keyName, result.version, {
  enabled: false
});

Deleting a key

The deleteKey method sets a key up for deletion. This process will happen in the background as soon as the necessary resources are available.

await client.deleteKey(keyName);

If soft-delete is enabled for the Key Vault, this operation will only label the key as a deleted key. A deleted key can't be updated. They can only be either read, recovered or purged.

await client.deleteKey(keyName);

// If soft-delete is enabled, we can eventually do:
await client.getDeletedKey(keyName);
// Deleted keys can also be recovered or purged:
await client.recoverDeletedKey(keyName);
// await client.purgeDeletedKey(keyName);

Since the deletion of a key won't happen instantly, some time is needed after the deleteKey method is called before the deleted key is available to be read, recovered or purged.

Cryptography

This library also offers a set of cryptographic utilities available through CryptographyClient. Similar to the KeysClient, CryptographyClient will connect to Azure Key Vault with the provided set of credentials. Once connected, CryptographyClient can encrypt, decrypt, sign, verify, wrap keys, and unwrap keys.

We can next connect to the key vault service just as we do with the KeysClient. We'll need to copy some settings from the key vault we are connecting to into our environment variables. Once they are in our environment, we can access them with the following code:

import { DefaultAzureCredential } from "@azure/identity";
import { KeysClient, CryptographyClient } from "@azure/keyvault-keys";

// DefaultAzureCredential expects the following three environment variables:
// * AZURE_TENANT_ID: The tenant ID in Azure Active Directory
// * AZURE_CLIENT_ID: The application (client) ID registered in the AAD tenant
// * AZURE_CLIENT_SECRET: The client secret for the registered application
const credential = new DefaultAzureCredential();

// Build the URL to reach your key vault
const vaultName = "<YOUR KEYVAULT NAME>";
const url = `https://${vaultName}.vault.azure.net`;

// Connect to the key vault service
const keysClient = new KeysClient(url, credential);

// Create or retrieve a key from the keyvault
let myKey = await keysClient.createKey("MyKey", "RSA");

// Lastly, create our cryptography client and connect to the service
// This example uses the URL that is part of the key we created (called key ID or kid)
const cryptographyClient = new CryptographyClient(url, myKey.keyMaterial!.kid!, credential);

Encrypt

encrypt will encrypt a message. The following algorithms are currently supported: "RSA-OAEP", "RSA-OAEP-256", and "RSA1_5".

const encrypt = await cryptographyClient.encrypt("RSA1_5", Buffer.from("My Message"));
console.log("encrypt result: ", encrypt);

Decrypt

decrypt will decrypt an encrypted message. The following algorithms are currently supported: "RSA-OAEP", "RSA-OAEP-256", and "RSA1_5".

const decrypt = await cryptographyClient.decrypt("RSA1_5", encrypt.result);
console.log("decrypt: ", decrypt.toString());

Sign

sign will cryptographically sign the digest (hash) of a message with a signature. The following algorithms are currently supported: "PS256", "PS384", "PS512", "RS256", "RS384", "RS512", "ES256","ES256K", "ES384", and "ES512".

const signatureValue = "MySignature";
let hash = crypto.createHash("sha256");

hash.update(signatureValue);
let digest = hash.digest();
console.log("digest: ", digest);

const signature = await cryptoClient.sign("RS256", digest);
console.log("sign result: ", signature);

Sign Data

signData will cryptographically sign a message with a signature. The following algorithms are currently supported: "PS256", "PS384", "PS512", "RS256", "RS384", "RS512", "ES256","ES256K", "ES384", and "ES512".

const signature = await cryptoClient.signData("RS256", Buffer.from("My Message"));
console.log("sign result: ", signature);

Verify

verify will cryptographically verify that the signed digest was signed with the given signature. The following algorithms are currently supported: "PS256", "PS384", "PS512", "RS256", "RS384", "RS512", "ES256","ES256K", "ES384", and "ES512".

const verifyResult = await cryptoClient.verify("RS256", digest, signature.result);
console.log("verify result: ", verifyResult);

Verify Data

verifyData will cryptographically verify that the signed message was signed with the given signature. The following algorithms are currently supported: "PS256", "PS384", "PS512", "RS256", "RS384", "RS512", "ES256","ES256K", "ES384", and "ES512".

const buffer = Buffer.from("My Message");
const verifyResult = await cryptoClient.verifyData("RS256", buffer, signature.result);
console.log("verify result: ", verifyResult);

Wrap Key

wrapKey will wrap a key with an encryption layer. The following algorithms are currently supported: "RSA-OAEP", "RSA-OAEP-256", and "RSA1_5".

const wrapped = await cryptoClient.wrapKey("RSA-OAEP", keyToWrap);
console.log("wrap result:", wrapped);

Unwrap Key

unwrapKey will unwrap a wrapped key. The following algorithms are currently supported: "RSA-OAEP", "RSA-OAEP-256", and "RSA1_5".

const unwrapped = await cryptoClient.unwrapKey("RSA-OAEP", wrapped.result);
console.log("unwrap result: ", unwrapped);

Troubleshooting

Enable logs

You can set the following environment variable to get the debug logs when using this library.

• Getting debug logs from the Key Vault Keys SDK

export DEBUG=azure*

Next steps

Please take a look at the samples directory for detailed examples on how to use this library.

Contributing

This project welcomes contributions and suggestions. Please read the contributing guidelines for detailed information about how to contribute and what to expect while contributing.

Testing

To run our tests, first install the dependencies (with npm install or rush install), then run the unit tests with: npm run unit-test. Our unit tests that target the behavior of our library against remotely available endpoints are executed using previously recorded HTTP request and responses.

Our integration tests will run against the live resources, which are determined by the environment variables you provide. To run the integration tests, you can run npm run integration-test, but make sure to provide the following environment variables:

• AZURE_CLIENT_ID: The Client ID of your Azure account.
• AZURE_CLIENT_SECRET: The secret of your Azure account.
• AZURE_TENANT_ID: The Tenant ID of your Azure account.
• KEYVAULT_NAME: The name of the Key Vault you want to run the tests against.

WARNING: Integration tests will wipe all of the existing records in the targeted Key Vault.

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.