Import a key from a web service

Securely upload an external customer key onto your instance using import a key from a web service (for example the key REST API). Both symmetric and asymmetric public keys can be imported into a targeted KMF cryptographic module.

The key to be imported (the target key) must be encrypted with a wrapping key before it's uploaded into the instance’s target cryptographic module. This wrapping key is the public component of a public/private key pair, which must be present on the instance. The key is a pre-requisite before the wrapped target key can be uploaded via Import From Web Services.

These two separate procedures (importing the wrapping key pair and importing the wrapped target key from a web service) are detailed in the following documentation. This key pair must be generated and uploaded to be available in the instance’s internal Key Import cryptographic module.

Note: This example uses OpenSSL for key and certificate generation and the Postman API test tool to show REST API use. Substitute other comparable tools based on your company requirements.

Parent Topic:Key Management Framework

Import the wrapping / unwrapping key pair

Configure Key Management Framework import settings before importing a key.

Before you begin

Role required: sn_kmf.cryptographic_manager

About this task

This example uses OpenSSL for key and certificate generation. Substitute other comparable tools based on your company requirements.

Procedure

1. In your local environment, use the terminal to create a certificate.

   For example: openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:4096 -keyout wrapping_private.key -out wrapping_public.crt

   This certificate is a public component that contains a key. The certificate is used to wrap an AES symmetric key.

2. In your local environment, use the terminal to create a keystore containing public cert (with the wrapping key), and private unwrapping key.

   For example:openssl pkcs12 -export -in wrapping_public.crt -inkey wrapping_private.key -name "wrapping_key_alias" -out wrapping_keystore.p12

3. On your instance, navigate to All > Key Management > Import Settings > Key Import Settings.

4. In the Algorithm Definition section, verify the Crypto Purpose is set to Asymmetric Key Unwrapping.

1. Select an appropriate algorithm that aligns with asymmetric key material for the imported keystore.

   See Cryptographic specification overview for additional information.

2. Select Next.

3. In the Lifecycle Definition section, select Next to continue.

4. In the Key Origin section, select either Import from PKCS12 or Import from BCFKS in the Origin field.

   Note: If using the example keystore from step 1, select Import from PKCS12.

5. Enter a Key Alias to identify the key.

   This alias should match the key alias (or “friendly name”) that was specified when generating the certificate or keystore to be uploaded. Continuing the example above, this would be wrapping_key_alias.

6. Select Next.

   The Key Creation section includes an Import Key link, which displays a dialog to upload the keystore. Continuing the example, this would be wrapping_keystore.p12.

Import a wrapped key from a web service

Upload your wrapped key into a cryptographic module using the import key from web service functionality. The example uses a symmetric key. Similar steps can be used to import an asymmetric key.

Before you begin

Role required: sn_kmf.cryptographic_manager (module configuration), sn_kmf.cryptographic_operator (REST operation basic authentication)

About this task

KMF Import key endpoint access is required to complete the key import process.

This example uses OpenSSL to generate keys and certificates. You may substitute other comparable tools based on your requirements.

Procedure

1. Using the terminal on your local device, wrap your symmetric key using the Key Import module public key wrapping key.

   For example: openssl pkeyutl -encrypt -pubin -inkey public_wrapping_key.pem -in symmetric_key.bin -pkeyopt rsa_padding_mode:oaep -pkeyopt rsa_oaep_md:sha256 -out wrapped_symmetric_key.txt

   This example creates a wrapped key file named wrapped_symmetric_key.txt.

2. Create a cryptographic module to be tied to the API.

   See or for additional information.

3. Add a cryptographic specification with the following selections.

   • Crypto Purpose: Symmetric Data Encryption/Decryption.
   • Key Origin: Import from web service

    See or for more information.

1. Execute an HTTP POST request to the import from a web service REST endpoint.

Successful import of the public key results in an HTTP response message with `Status 200`.

1. Verify that the key successfully imported to the targeted cryptographic module.