dogtagpki

#199 Refactor audit code
Closed: fixed by edewata. Opened by edewata.

Closed: fixed
Reopen Issue

A new Auditor service was added in ticket #160 and the AdminServlet has been refactored to use the new service. However, there are 20 other places where the CMS.getSignedAuditLogger() is called directly, thus duplicating the audit code such as audit(), auditSubjectID(), auditGroupID(), auditGroups(). They all should be refactored to use the new Auditor service.

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

@edewata Can this be closed? I don't see any current usages of getSignedAuditLogger(...) in the CMS code.

Metadata Update from @cipherboy:
- Custom field feature adjusted to None
- Custom field proposedmilestone adjusted to None (was: Future)
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: None

As of PKI 10.8 the CMS.getSignedAuditLogger() no longer exists, so I'm closing this ticket. Note that there's a separate effort to convert audit events created using AuditEvent class into subclasses of SignedAuditEvent.

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

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

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
None
None
None
None
Normal
None
None
None
defect
General
Community
trivial
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.