This is a negative test for audit event filter.
When an incorrect format is applied for audit event filter, pki should fail to start.
Steps to Reproduce:
1.configure CS.cfg as below Adding extra closing bracket at the end. log.instance.SignedAudit.filters.CERT_REQUEST_PROCESSED=(InfoName=cancelReason)) 2. restart the instance 3. generate a cert request pki -d /opt/nssdb -c Secret123 -h pki1.example.com -p 20080 client-cert-request uid=testuser 4. cancel the request pki -d /opt/nssdb -c Secret123 -h pki1.example.com -p 20080 -n "PKI CA Administrator for Example.Org" ca-cert-request-review 41 --action cancel 5. check the audit log
Actual results:
this some how acts as not filter and events do not appear with InfoName=cancelReason
Expected results:
PKI should not have started at all.
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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1533474 - Custom field type adjusted to None - Custom field version adjusted to None
Per 10.5.x/10.6 Triage: 10.6
edewata: negative case
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/3046
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
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)
Login to comment on this ticket.