Cloning nonvariant PGP keys by using the System-generated flow

You can clone a nonvariant PGP key by using the System-generated flow.

About this task

For cloning, refer to the following procedure.

Procedure

  1. From the PGP keys list page, select a PGP key to clone.
    The PGP key details page opens.
  2. From the Production or CTE tab, select a version of the PGP key you want to clone.
    The Clone key action is unavailable until you select a PGP key version previously deployed. The action also remains unavailable when you select the latest deployed version of the PGP key.
  3. After you select a PGP key version that you want to clone, click Clone key.
  4. Optional: On the Clone PGP key modal, enter the reason for cloning the PGP key in the Reason for cloning (optional) text field.
  5. Click Clone.
    Clicking Clone creates and deploys a cloned version of the PGP key to both the CTE and production environments.
    A new version of the PGP key is now created. The status of the PGP key is changed from Final to Work in progress. You can view information on the banner.
  6. Optional: On the CTE configurations page, edit the following PGP key properties:
    • Update the Email ID.
    • Select the Key algorithm type from the drop down.
    • Select the Key size (in bits) from the drop down.
    • Toggle Set key to expire to enable it.
    • Update the description by using the Description (optional) text field.
  7. To re-generate a PGP public key by using the same passphrase, select the Yes option. Otherwise, select No.
  8. To re-generate a new PGP public key, click Re-gerenate key.
  9. Click Deploy to CTE.
  10. To test your PGP key on a connection, select the Yes check box.
  11. To deploy the new PGP key version to production, click Deploy to production.
    The new PGP key version is now live and has the Live in production tag. You can view information on the banner. The status of the key changes from Work in progress to Final. And the lock icon changes from Unlock to Lock to indicate that the PGP key is ready to be locked by another user.