IBM Cloud Docs
Managing EP11 keys with the UI

Managing EP11 keys with the UI

Apart from using the Hyper Protect Crypto Services PKCS #11 API to generate and use Enterprise PKCS #11 (EP11) keys, you can also use the UI to view, create, and delete EP11 keys.

Before you begin

Before you can manage EP11 keystores and keys with the UI, complete the following steps to open your Hyper Protect Crypto Services dashboard:

  1. Log in to the UI.
  2. Go to Menu > Resource list to view a list of your resources.
  3. From your IBM Cloud resource list, select your provisioned instance of Hyper Protect Crypto Services and click the instance name.
  4. Create an EP11 keystore to store the key. The keystore can be created through the UI UI or through the PKCS #11 API.

Viewing EP11 keys

For default service access roles that support viewing EP11 keys, see service access roles. If you are to create custom roles, make sure to assign the following actions to the custom role:

  • hs-crypto.keystore.listkeystoresbyids
  • hs-crypto.keystore.listkeysbyids

For instructions on creating custom roles, see Creating custom roles.

On the Hyper Protect Crypto Services dashboard, do the following to view EP11 key details:

  1. To view a list of created EP11 keys, select the EP11 keys tab in the side menu.

    An EP11 key table is displayed with the following details.

    Table 1. Describes the EP11 keys table
    Property Description
    ID The unique identifier that is assigned when the key is created.
    Name A human-readable alias for easy identification of your key. The value of the CKA_LABEL key attribute is displayed in this field. The key name might not be unique. You can assign multiple keys with the same name. However, it is suggested to assign a unique name to each key in the same keystore for easy identification.
    Class The class of the key. Possible values are Public, Private, and Secret. The value is determined by the CKA_CLASS key attribute. Public indicates that the key is the public key of an asymmetric key pair. Private indicates that the key is the private key of an asymmetric key pair. Secret indicates that the key is a symmetric key.
    Version The version number of the key. When the key is first created, version 0 is assigned. The version number is increased by 1 sequentially upon each update, such as using the C_SetAttributeValue function to update a key attribute value.
    Keystore The unique identifier of the keystore the key is stored in.
    Type The type of the EP11 key that is managed in Hyper Protect Crypto Services.
  2. To view details of the key attributes, click the Actions icon Actions icon of the key row, and then select Show more details.

    You can also identify the public key, the private key, and the symmetric key by checking the value of the CKA_CLASS attribute. CKO_PUBLIC_KEY indicates a public key; CKO_PRIVATE_KEY indicates a private key; CKO_SECRET_KEY indicates a symmetric key.

Creating EP11 keys

For default service access roles that support creating EP11 keys, see service access roles. If you are to create custom roles, make sure to assign the following actions to the custom role:

  • hs-crypto.keystore.listkeystoresbyids
  • hs-crypto.keystore.listkeysbyids
  • hs-crypto.crypto.generatekey
  • hs-crypto.crypto.generatekeypair
  • hs-crypto.keystore.storenewkey

For instructions on creating custom roles, see Creating custom roles.

Complete the following steps to create an EP11 key:

  1. Select the EP11 keys tab in the side menu. You can see a list of existing EP11 keys with each having a unique ID.

  2. Click Create key. In the Create EP11 key panel that is displayed, complete the following steps:

    1. Specify the following key details on the Identifier page:

      Table 2. Describes the Identifier page
      Setting Description
      Key name A human-readable alias for easy identification of your key. The key name length can be 1-32 characters. To protect your privacy, ensure that the key name does not contain personally identifiable information (PII), such as your name or location. The key name might not be unique. You can assign multiple keys with the same name. However, it is suggested to assign a unique name to each key in the same keystore for easy identification.
      Key type The type of the EP11 key that you want to manage in Hyper Protect Crypto Services.
      Keystore The unique identifier of the keystore with the keystore type appended. Choose one that you want the key to be stored in from the list. For an asymmetric key pair, you need to specify the keystore separately to store the public key and the private key. You can find all available keystores by clicking the EP11 keystores tab in the side menu.

      By default, two key IDs are automatically generated. One is for the public key, and the other is for the private key. However, if you select a symmetric key type, such as an AES key, a DES key, or a Generic key, only one key ID is shown on the page.

    2. Specify key attributes by following these steps:

      • If you are creating an asymmetric key, specify key attributes on the Public key attributes and Private key attributes pages:

        1. The required attributes are listed with the default values. To modify the attribute values, click the Edit icon Edit icon.

        2. To add more attributes, click Add public attribute or Add private attribute depending on which page you are on. For a list of supported attributes, see supported attributes table and supported curve names for Elliptic Curve keys.

          Add and set the CKA_MODIFIABLE attribute to true if you want to modify the added key later.

        3. (Optional) You can delete more attributes by clicking the Trash can icon Trash can icon. The required attributes cannot be deleted.

        4. Click Next to continue.

      • If you are creating a symmetric key, such as an AES key, a DES key, and a Generic key, specify key attributes on the Key attributes page:

        1. The required attributes are listed with the default values. To modify the attribute values, click the Edit icon Edit icon.
        2. To add more attributes, click Add attributes. For a list of supported attributes, see supported attributes table.
        3. (Optional) You can delete more attributes by clicking the Trash can icon Trash can icon. The required attributes cannot be deleted.
        4. Click Next to continue.
    3. On the Confirmation page, verify the key details and click Create key.

      1. Verify the key details that are displayed, especially the key type, keystore, and key attributes.

        All the values cannot be modified through the UI after the key is created.

      2. Click Create key to confirm the creation.

If you are performing cryptographic operations using the PKCS #11 API, to load the created key from UI to your PKCS #11 application, reinitialize the PKCS #11 API by using the C_Finalize() and C_Initialize() functions.

You have successfully created an EP11 key. The created key is displayed as the first row in the Enterprise PKCS #11 keys table.

Deleting EP11 keys

For default service access roles that support deleting EP11 keys, see service access roles. If you are to create custom roles, make sure to assign the following actions to the custom role:

  • hs-crypto.keystore.listkeystoresbyids
  • hs-crypto.keystore.listkeysbyids
  • hs-crypto.keystore.deletekey

For instructions on creating custom roles, see Creating custom roles.

If you want to delete an EP11 key, complete the following steps:

After you delete an EP11 key, you are not able to access the data associated with the key. This action cannot be undone.

  1. Select the EP11 keys tab in the side menu, and find the key that you want to delete in the list.
  2. Click the Actions icon Actions icon in the key row, and click Delete key.
  3. Verify the ID of the key to be deleted, and check the box to confirm the deletion.
  4. Click Delete keystore.

If you are performing cryptographic operations using the PKCS #11 API, to delete the key in your PKCS #11 application, reinitialize the PKCS #11 API by using the C_Finalize() and C_Initialize() functions.

What's next

You can use EP11 keys for cryptographic operations with the PKCS #11 API. For more information, see Performing cryptographic operations with the PKCS #11 API and PKCS #11 API reference.