#2694 Incorrect audit event outcome for agent-canceled cert request.
Closed: fixed 6 years ago Opened 6 years ago by edewata.

This is similar to ticket #2693.

Currently when an agent cancels a certificate request the server will generate a CERT_REQUEST_PROCESSED with [Outcome=Success]. The correct log should have [Outcome=Failure].

For example, consider the following command:

$ pki -d ~/.dogtag/pki-tomcat/ca/alias/ -c Secret.123 -n caadmin ca-cert-request-review 7 --action cancel

Currently it generates the following log:

[AuditEvent=CERT_REQUEST_PROCESSED][SubjectID=caadmin][Outcome=Success][ReqID=7]
[InfoName=cancelReason][InfoValue=<null>] certificate request processed

It should generate the following log:

[AuditEvent=CERT_REQUEST_PROCESSED][SubjectID=caadmin][Outcome=Failure][ReqID=7]
[InfoName=cancelReason][InfoValue=<null>] certificate request processed

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

6 years ago

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

6 years ago

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1452250
- Issue assigned to edewata

6 years ago

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

6 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/2814

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.

Login to comment on this ticket.

Metadata