Regenerate the Publisher Signing Key

Regenerate the Publisher signing key whenever you need to renew the Publisher signing key or create a replacement key with a specific length or expiration period. For example, you might need a signing key that expires after a defined period to meet a receiving bank’s requirements.

If Publisher still uses legacy 1024-bit signing keys, you see the following message advising you to regenerate the Publisher signing key as 2048, 3072, or 4096-bit keys.

Warning This keystore's BI Publisher PGP signing key uses DSA 1024-bit, which will not be supported in upcoming releases. To avoid PGP signing or encryption disruption, click Regenerate BI Publisher Key to regenerate it with a supported algorithm and length.

Note:

You no longer need to request assistance from Oracle Support to regenerate the Publisher signing key.

1. Configure the required RSA key length and expiration period using PGP encryption properties. See Configure PGP Signing Key Encryption Properties.
2. From the Administration page, under Security Center, select PGP Keys.
3. Select Regenerate BI Publisher Key.
4. Review the confirmation warning.
   Regenerating the key replaces the current Publisher signing key.
5. Confirm the operation.
6. After regeneration completes, download the new Publisher public key.

   An error displays if regeneration can’t complete because an incompatible existing key is present. Resolve the incompatible-key and try again.

7. Import the new public key into every destination system that verifies Publisher signatures.
8. Test signed report delivery and signature verification.