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
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.
Per Bug Triage of 05/05/2016: 10.4
Metadata Update from @rpattath: - Issue set to the milestone: UNTRIAGED
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)
Per 10.5.x/10.6 Triage: FUTURE
mharmsen: publishing not a priority for RHEL 7.x
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/2132
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.