#2839 Missing authority ID in LWCA signing audit events.
Closed: migrated by dmoluguw. Opened by edewata.

Ticket #2654 added new signing info audit events at startup time to record which keys will be used by each CA (i.e. host CA or LWCA) for cert and OCSP signing later. However, at the actual cert or OCSP signing itself, the current audit event does not indicate which LWCA actually does the signing so the key cannot be determined. To fix the problem, the cert and OCSP signing events for LWCA should be modified to include the LWCA ID (i.e. authority ID).

Cert signing:

  • https://github.com/dogtagpki/pki/blob/e16be807c2cca6d717dad550343b6aeff347d91b/base/ca/src/com/netscape/ca/CAService.java#L862

OCSP signing:

  • https://github.com/dogtagpki/pki/blob/e16be807c2cca6d717dad550343b6aeff347d91b/base/ca/src/com/netscape/ca/CertificateAuthority.java#L2437
  • https://github.com/dogtagpki/pki/blob/e16be807c2cca6d717dad550343b6aeff347d91b/base/server/cms/src/com/netscape/cms/ocsp/DefStore.java#L406
  • https://github.com/dogtagpki/pki/blob/e16be807c2cca6d717dad550343b6aeff347d91b/base/server/cms/src/com/netscape/cms/ocsp/LDAPStore.java#L353

Metadata Update from @mharmsen:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

Per PKI Team Meeting of 20171109: Future

Metadata Update from @mharmsen:
- Issue set to the milestone: FUTURE (was: 0.0 NEEDS_TRIAGE)

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/2959

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)

Metadata