pki should not starts up for incorrect Audit event filter format.

[pki-bot]

This issue was migrated from Pagure Issue #2928. Originally filed by mharmsen (@mharmsen) on 2018-02-07 20:17:49:

• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1533474

---

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.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-02-07 20:18:09

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

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-04-10 22:18:10

Per 10.5.x/10.6 Triage: 10.6

edewata: negative case