dogtagpki

#2738 Auditing: ReqID usage inconsistency for CertStatusChangeRequestProcessedEvent and cert requests
Closed: fixed Opened by mharmsen.

Closed: fixed
Reopen Issue

I found the following in my audit log:

[AuditEvent=CERT_STATUS_CHANGE_REQUEST_PROCESSED][SubjectID=Lady Christina Fu][
Outcome=Success][ReqID=caadmin][CertSerialNum=33][RequestType=revoke][RevokeRea
sonNum=Unspecified][Approval=complete] certificate status change request
processed

If you search for PROFILE_CERT_REQUEST or CERT_REQUEST_PROCESSED events in the
audit log, you will see that ReqID is supposed to be the actual request id
processed.

while I agree the RequestID should be included in the
CERT_STATUS_CHANGE_REQUEST_PROCESSED event as well, but recall what I said
about "consistent tags" for audit searching, this should be fixed.

We can discuss whether we should add an additional field of "RequesterID".

Metadata Update from @mharmsen:
- 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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1461217
- Custom field type adjusted to defect
- Custom field version adjusted to ''
- Issue priority set to: critical
- Issue set to the milestone: 10.4

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:
- Issue assigned to edewata

Fixed in master:

  • https://github.com/dogtagpki/pki/commit/28d4187122f358d3203fe0bca26960f179649eb9
  • https://github.com/dogtagpki/pki/commit/76eca860d5d87b78156d1478306e8efab0c2c9e1

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.5.0 (was: 10.5)
- Issue status updated to: Closed (was: Open)

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

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.5.1-1.fc27

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

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
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.