encryption – Client-Side Field Level Encryption

Support for explicit client-side field level encryption.

class pymongo.encryption.Algorithm

An enum that defines the supported encryption algorithms.

class pymongo.encryption.ClientEncryption(kms_providers, key_vault_namespace, key_vault_client, codec_options)

Explicit client-side field level encryption.

The ClientEncryption class encapsulates explicit operations on a key vault collection that cannot be done directly on a MongoClient. Similar to configuring auto encryption on a MongoClient, it is constructed with a MongoClient (to a MongoDB cluster containing the key vault collection), KMS provider configuration, and keyVaultNamespace. It provides an API for explicitly encrypting and decrypting values, and creating data keys. It does not provide an API to query keys from the key vault collection, as this can be done directly on the MongoClient.

See Explicit Encryption for an example.

  • Parameters

    • kms_providers: Map of KMS provider options. Two KMS providers are supported: “aws” and “local”. The kmsProviders map values differ by provider:

      • aws: Map with “accessKeyId” and “secretAccessKey” as strings. These are the AWS access key ID and AWS secret access key used to generate KMS messages. An optional “sessionToken” may be included to support temporary AWS credentials.

      • azure: Map with “tenantId”, “clientId”, and “clientSecret” as strings. Additionally, “identityPlatformEndpoint” may also be specified as a string (defaults to ‘login.microsoftonline.com’). These are the Azure Active Directory credentials used to generate Azure Key Vault messages.

      • gcp: Map with “email” as a string and “privateKey” as bytes or a base64 encoded string (unicode on Python 2). Additionally, “endpoint” may also be specified as a string (defaults to ‘oauth2.googleapis.com’). These are the credentials used to generate Google Cloud KMS messages.

      • local: Map with “key” as bytes (96 bytes in length) or a base64 encoded string (unicode on Python 2) which decodes to 96 bytes. “key” is the master key used to encrypt/decrypt data keys. This key should be generated and stored as securely as possible.

    • key_vault_namespace: The namespace for the key vault collection. The key vault collection contains all data keys used for encryption and decryption. Data keys are stored as documents in this MongoDB collection. Data keys are protected with encryption by a KMS provider.

    • key_vault_client: A MongoClient connected to a MongoDB cluster containing the key_vault_namespace collection.

    • codec_options: An instance of CodecOptions to use when encoding a value for encryption and decoding the decrypted BSON value. This should be the same CodecOptions instance configured on the MongoClient, Database, or Collection used to access application data.

New in version 3.9.

  • close()

    Release resources.

    Note that using this class in a with-statement will automatically call close():

    1. with ClientEncryption(...) as client_encryption:
    2. encrypted = client_encryption.encrypt(value, ...)
    3. decrypted = client_encryption.decrypt(encrypted)
  • create_data_key(kms_provider, master_key=None, key_alt_names=None)

    Create and insert a new data key into the key vault collection.

    • Parameters

      • kms_provider: The KMS provider to use. Supported values are “aws” and “local”.

      • master_key: Identifies a KMS-specific key used to encrypt the new data key. If the kmsProvider is “local” the master_key is not applicable and may be omitted.

        If the kms_provider is “aws” it is required and has the following fields:

        1. - `region` (string): Required. The AWS region, e.g. "us-east-1".
        2. - `key` (string): Required. The Amazon Resource Name (ARN) to
        3. the AWS customer.
        4. - `endpoint` (string): Optional. An alternate host to send KMS
        5. requests to. May include port number, e.g.
        6. "kms.us-east-1.amazonaws.com:443".

        If the kms_provider is “azure” it is required and has the following fields:

        1. - `keyVaultEndpoint` (string): Required. Host with optional
        2. port, e.g. "example.vault.azure.net".
        3. - `keyName` (string): Required. Key name in the key vault.
        4. - `keyVersion` (string): Optional. Version of the key to use.

        If the kms_provider is “gcp” it is required and has the following fields:

        1. - `projectId` (string): Required. The Google cloud project ID.
        2. - `location` (string): Required. The GCP location, e.g. "us-east1".
        3. - `keyRing` (string): Required. Name of the key ring that contains
        4. the key to use.
        5. - `keyName` (string): Required. Name of the key to use.
        6. - `keyVersion` (string): Optional. Version of the key to use.
        7. - `endpoint` (string): Optional. Host with optional port.
        8. Defaults to "cloudkms.googleapis.com".
      • key_alt_names (optional): An optional list of string alternate names used to reference a key. If a key is created with alternate names, then encryption may refer to the key by the unique alternate name instead of by key_id. The following example shows creating and referring to a data key by alternate name:

        1. client_encryption.create_data_key("local", keyAltNames=["name1"])
        2. # reference the key with the alternate name
        3. client_encryption.encrypt("457-55-5462", keyAltName="name1",
        4. algorithm=Algorithm.AEAD_AES_256_CBC_HMAC_SHA_512_Random)

      Returns

      The _id of the created data key document as a Binary with subtype UUID_SUBTYPE.

  • decrypt(value)

    Decrypt an encrypted value.

    • Parameters

      • value (Binary): The encrypted value, a Binary with subtype 6.

      Returns

      The decrypted BSON value.

  • encrypt(value, algorithm, key_id=None, key_alt_name=None)

    Encrypt a BSON value with a given key and algorithm.

    Note that exactly one of key_id or key_alt_name must be provided.

    • Parameters

      • value: The BSON value to encrypt.

      • algorithm (string): The encryption algorithm to use. See Algorithm for some valid options.

      • key_id: Identifies a data key by _id which must be a Binary with subtype 4 ( UUID_SUBTYPE).

      • key_alt_name: Identifies a key vault document by ‘keyAltName’.

      Returns

      The encrypted value, a Binary with subtype 6.