#768 Cloning a Stand-alone DRM
Closed: migrated 2 years ago by dmoluguw. Opened 9 years ago by mharmsen.

A stand-alone DRM was created via the following TRAC Tickets:

One of the next phases in this development will be to provide cloning from this stand-alone DRM (see http://pki.fedoraproject.org/wiki/Stand-alone_PKI_Subsystems#Case_II:_DRM_Cloned_from_Stand-alone_DRM).

During development of the stand-alone DRM, a number of servlets were added to the web.xml file whose use could not be verified until a stand-alone DRM could be cloned which would use the stand-alone DRM as its security domain, thus the following "cleanup" task needs to be verified as a part of the development of the feature described in this ticket:

  • Confirm whether or not all of the servlets/mappings added to support Stand-alone PKI actually need to be exposed in web.xml. (HINT: Use Access Log to verify this.)

Metadata Update from @mharmsen:
- Issue set to the milestone: UNTRIAGED

5 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/1335

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.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata