dogtagpki

#2635 Audit event improvements
Closed: duplicate Opened by edewata.

Closed: duplicate
Reopen Issue

There are improvements that need to be done with the current audit events.

In the first phase the current code needs to be inspected to make sure it works properly. That includes verifying/fixing existing code that generates audit events to ensure all parameters are correct and complete. Due to the amount of code that needs inspection, this task may be split into smaller tasks.

The second phase includes some additional changes:

  • enabling/disabling certain audit events by default
  • splitting certain audit events into more specific events
  • modifying certain audit events to include searchable fields

Phase I (ensuring audit log correctness) has been split into the following tickets:

  • CA: https://pagure.io/dogtagpki/issue/2636
  • KRA: https://pagure.io/dogtagpki/issue/2637
  • OCSP: https://pagure.io/dogtagpki/issue/2638
  • TKS: https://pagure.io/dogtagpki/issue/2639
  • TPS: https://pagure.io/dogtagpki/issue/2640
  • Common: https://pagure.io/dogtagpki/issue/2641

Metadata Update from @edewata:
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field origin adjusted to Community
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field type adjusted to defect
- Custom field version adjusted to ''

Metadata Update from @edewata:
- Issue priority set to: critical
- Issue set to the milestone: 10.4

Phase II has been split into the following tickets:

  • https://pagure.io/dogtagpki/issue/2647
  • https://pagure.io/dogtagpki/issue/2648
  • https://pagure.io/dogtagpki/issue/2649
  • https://pagure.io/dogtagpki/issue/2650
  • https://pagure.io/dogtagpki/issue/2651
  • https://pagure.io/dogtagpki/issue/2652
  • https://pagure.io/dogtagpki/issue/2653
  • https://pagure.io/dogtagpki/issue/2654
  • https://pagure.io/dogtagpki/issue/2655
  • https://pagure.io/dogtagpki/issue/2656
  • https://pagure.io/dogtagpki/issue/2657
  • https://pagure.io/dogtagpki/issue/2686
Edited by edewata

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1404075, https://bugzilla.redhat.com/show_bug.cgi?id=1445532

Metadata Update from @mharmsen:
- Issue assigned to edewata

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.4)

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

Per CS/DS Meeting 09/25/2017: 10.5 blocker

Metadata Update from @mharmsen:
- Issue priority set to: blocker (was: major)

Metadata Update from @edewata:
- Assignee reset

Duplicate of tickets #2607 and #2608.

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

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.0 (was: 10.5)

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

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
Lowest
defect
General
''
''
Community
''
''
''
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.