publishing fails when rule has a predicate specified

[pki-bot]

This issue was migrated from Pagure Issue #1573. Originally filed by rpattath (@rpattath) on 2015-08-19 21:19:18:

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

---

file based publishing fails when rule has a predicate specified

Steps to Reproduce:

enable publishing.
delete all existing rules
create a rule { rule1 }

    the ruleType = certs ,
    predicate = HTTP_PARAMS.certType==client
    uses a filebasedpublisher ( file1 )  with noMap ( map1 )

configure filebasedpublisher ( file1 )  such that it would publish to a
writable directory like /export/
configure filebasedpublisher ( file1 )  such that it would publish .der and
.b64 type files
enroll for a user certificate using the profile caUserCert and approve it.
enroll for a server certificate using the profile caServerCert and approve it.

Actual results:

publishing of client cert fails

Expected results:

publishing of client certs should be successful. publishing of server cert
should fail

Additional info:

CA debug log messages

[18/Aug/2015:17:56:20][Thread-28]: LdapRequestListener handling publishing for
enrollment request id 90
[18/Aug/2015:17:56:20][Thread-28]: Checking publishing for request 90
[18/Aug/2015:17:56:20][Thread-28]: In  PublisherProcessor::publishCert
[18/Aug/2015:17:56:20][Thread-28]: Publishing: can't find publishing
rule,exiting routine.
[18/Aug/2015:17:56:20][Thread-28]: PublishProcessor::publishCert : Failed to
publish using rule: No rules enabled
[18/Aug/2015:17:56:20][Thread-28]: RunListeners: IRequestListener =
com.netscape.cms.listeners.CertificateRevokedListener
[18/Aug/2015:17:56:20][Thread-28]: RunListeners: mRequest = 90
[18/Aug/2015:17:56:20][Thread-28]: updatePublishingStatus
mSavePublishingCounter: 9 mSavePublishingStatus: 200
[18/Aug/2015:17:56:20][Thread-28]: RunListeners:  noQueue  SingleRequest
[18/Aug/2015:17:56:20][Thread-28]: RequestRepository:  setPublishingStatus
mBaseDN: ou=ca,ou=requests,dc=pki-ca  status: -1
[18/Aug/2015:17:56:20][Thread-28]: In LdapBoundConnFactory::getConn()
[18/Aug/2015:17:56:20][Thread-28]: masterConn is connected: true
[18/Aug/2015:17:56:20][Thread-28]: getConn: conn is connected true
[18/Aug/2015:17:56:20][Thread-28]: getConn: mNumConns now 5
[18/Aug/2015:17:56:20][Thread-28]: returnConn: mNumConns now 6
[18/Aug/2015:17:56:20][Thread-28]: Number of publishing threads: 0

[pki-bot]

Comment from mharmsen (@mharmsen) at 2015-08-20 03:45:59

08/19/2015 -- After this was determined to not be a regression, but just a bug, it is being pushed out to the Dogtag 10.3 timeframe.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-05-06 22:34:51

Per Bug Triage of 05/05/2016: 10.4

[pki-bot]

Comment from rpattath (@rpattath) at 2017-02-27 13:58:58

Metadata Update from @rpattath:

• Issue set to the milestone: UNTRIAGED

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-30 22:43:07

Metadata Update from @mharmsen:

• Custom field feature adjusted to None
• Custom field proposedmilestone adjusted to None
• Custom field proposedpriority adjusted to None
• Custom field reviewer adjusted to None
• Custom field version adjusted to None
• Issue close_status updated to: None
• Issue set to the milestone: FUTURE (was: UNTRIAGED)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-04-13 18:46:07

Per 10.5.x/10.6 Triage: FUTURE

mharmsen: publishing not a priority for RHEL 7.x