#733 Provide description of manual procedure which will allow to obtain issued transport certificate
Closed: Fixed None Opened 10 years ago by awnuk.

This is part of ticket #129 - RFE: Add support for multiple DRM transport keys.

This ticket will provide description of manual procedure which will allow to obtain issued transport certificate.

[[br]] Base on discussion with Nathan (nkinder) scope of this feature has been significantly reduced by only providing ability for DRM to support two transport keys: current key and new key. DRM will provide ability to automatically distinguish between its transport keys during archival process.

All other processes will be covered by manual procedures. This includes:

  • requesting new transport certificate
  • obtaining issued certificate
  • importing of new transport certificate and keys to DRM's NSS DB
  • updating of DRM configuration to reflect existence of new transport certificate and keys
  • propagation of new transport certificate and keys to DRM clones
  • replacement of the current transport certificate and keys during process of transfer of the new transport certificate and keys to become the current one.
  • propagation of new transport certificate to all CAs communicating with updated DRM (including CAs' clones)

Above list of procedures may grow.

Please note that all manual procedures are requiring subsystem restarts which are resulting in service interruptions.

\ \ ‚Äčhttps://bugzilla.redhat.com/show_bug.cgi?id=804677 (Red Hat Certificate System)


Here is how to retrieve DRM transport certificate:

  • Go to DRM's NSS DB directory [[br]] cd /etc/pki/pki-tomcat/alias
  • Wait for agent approval of submitted request to retrieve certificate by checking request status on EE retrieval page
  • Once new DRM transport certificate is available then paste base64 encoded certificate value into a text file [[br]] cert-<sn>.txt [[br]] Do not include header [[br]] -----BEGIN CERTIFICATE----- [[br]] or footer [[br]] -----END CERTIFICATE-----

For next step see: ticket:734#comment:2

Metadata Update from @awnuk:
- Issue assigned to awnuk
- Issue set to the milestone: 10.1 - 09/13 (September)

6 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1301

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata